[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWQXCE40XWT4FZ3VWZFGDP":3,"skill-same:01M7CWQXCE40XWT4FZ3VWZFGDP":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter",null,"Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-bounty-hunter\ndescription: Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.\nmetadata:\n  origin: ECC direct-port adaptation\nversion: \"1.0.0\"\n---\n\n# Security Bounty Hunter\n\nUse this when the goal is practical vulnerability discovery for responsible disclosure or bounty submission, not a broad best-practices review.\n\n## When to Use\n\n- Scanning a repository for exploitable vulnerabilities\n- Preparing a Huntr, HackerOne, or similar bounty submission\n- Triage where the question is \"does this actually pay?\" rather than \"is this theoretically unsafe?\"\n\n## How It Works\n\nBias toward remotely reachable, user-controlled attack paths and throw away patterns that platforms routinely reject as informative or out of scope.\n\n## In-Scope Patterns\n\nThese are the kinds of issues that consistently matter:\n\n| Pattern | CWE | Typical impact |\n| --- | --- | --- |\n| SSRF through user-controlled URLs | CWE-918 | internal network access, cloud metadata theft |\n| Auth bypass in middleware or API guards | CWE-287 | unauthorized account or data access |\n| Remote deserialization or upload-to-RCE paths | CWE-502 | code execution |\n| SQL injection in reachable endpoints | CWE-89 | data exfiltration, auth bypass, data destruction |\n| Command injection in request handlers | CWE-78 | code execution |\n| Path traversal in file-serving paths | CWE-22 | arbitrary file read or write |\n| Auto-triggered XSS | CWE-79 | session theft, admin compromise |\n\n## Skip These\n\nThese are usually low-signal or out of bounty scope unless the program says otherwise:\n\n- Local-only `pickle.loads`, `torch.load`, or equivalent with no remote path\n- `eval()` or `exec()` in CLI-only tooling\n- `shell=True` on fully hardcoded commands\n- Missing security headers by themselves\n- Generic rate-limiting complaints without exploit impact\n- Self-XSS requiring the victim to paste code manually\n- CI\u002FCD injection that is not part of the target program scope\n- Demo, example, or test-only code\n\n## Workflow\n\n1. Check scope first: program rules, SECURITY.md, disclosure channel, and exclusions.\n2. Find real entrypoints: HTTP handlers, uploads, background jobs, webhooks, parsers, and integration endpoints.\n3. Run static tooling where it helps, but treat it as triage input only.\n4. Read the real code path end to end.\n5. Prove user control reaches a meaningful sink.\n6. Confirm exploitability and impact with the smallest safe PoC possible.\n7. Check for duplicates before drafting a report.\n\n## Example Triage Loop\n\n```bash\nsemgrep --config=auto --severity=ERROR --severity=WARNING --json\n```\n\nThen manually filter:\n\n- drop tests, demos, fixtures, vendored code\n- drop local-only or non-reachable paths\n- keep only findings with a clear network or user-controlled route\n\n## Report Structure\n\n```markdown\n## Description\n[What the vulnerability is and why it matters]\n\n## Vulnerable Code\n[File path, line range, and a small snippet]\n\n## Proof of Concept\n[Minimal working request or script]\n\n## Impact\n[What the attacker can achieve]\n\n## Affected Version\n[Version, commit, or deployment target tested]\n```\n\n## Quality Gate\n\nBefore submitting:\n\n- The code path is reachable from a real user or network boundary\n- The input is genuinely user-controlled\n- The sink is meaningful and exploitable\n- The PoC works\n- The issue is not already covered by an advisory, CVE, or open ticket\n- The target is actually in scope for the bounty program\n","# Security Bounty Hunter\n\nUse this when the goal is practical vulnerability discovery for responsible disclosure or bounty submission, not a broad best-practices review.\n\n## When to Use\n\n- Scanning a repository for exploitable vulnerabilities\n- Preparing a Huntr, HackerOne, or similar bounty submission\n- Triage where the question is \"does this actually pay?\" rather than \"is this theoretically unsafe?\"\n\n## How It Works\n\nBias toward remotely reachable, user-controlled attack paths and throw away patterns that platforms routinely reject as informative or out of scope.\n\n## In-Scope Patterns\n\nThese are the kinds of issues that consistently matter:\n\n| Pattern | CWE | Typical impact |\n| --- | --- | --- |\n| SSRF through user-controlled URLs | CWE-918 | internal network access, cloud metadata theft |\n| Auth bypass in middleware or API guards | CWE-287 | unauthorized account or data access |\n| Remote deserialization or upload-to-RCE paths | CWE-502 | code execution |\n| SQL injection in reachable endpoints | CWE-89 | data exfiltration, auth bypass, data destruction |\n| Command injection in request handlers | CWE-78 | code execution |\n| Path traversal in file-serving paths | CWE-22 | arbitrary file read or write |\n| Auto-triggered XSS | CWE-79 | session theft, admin compromise |\n\n## Skip These\n\nThese are usually low-signal or out of bounty scope unless the program says otherwise:\n\n- Local-only `pickle.loads`, `torch.load`, or equivalent with no remote path\n- `eval()` or `exec()` in CLI-only tooling\n- `shell=True` on fully hardcoded commands\n- Missing security headers by themselves\n- Generic rate-limiting complaints without exploit impact\n- Self-XSS requiring the victim to paste code manually\n- CI\u002FCD injection that is not part of the target program scope\n- Demo, example, or test-only code\n\n## Workflow\n\n1. Check scope first: program rules, SECURITY.md, disclosure channel, and exclusions.\n2. Find real entrypoints: HTTP handlers, uploads, background jobs, webhooks, parsers, and integration endpoints.\n3. Run static tooling where it helps, but treat it as triage input only.\n4. Read the real code path end to end.\n5. Prove user control reaches a meaningful sink.\n6. Confirm exploitability and impact with the smallest safe PoC possible.\n7. Check for duplicates before drafting a report.\n\n## Example Triage Loop\n\n```bash\nsemgrep --config=auto --severity=ERROR --severity=WARNING --json\n```\n\nThen manually filter:\n\n- drop tests, demos, fixtures, vendored code\n- drop local-only or non-reachable paths\n- keep only findings with a clear network or user-controlled route\n\n## Report Structure\n\n```markdown\n## Description\n[What the vulnerability is and why it matters]\n\n## Vulnerable Code\n[File path, line range, and a small snippet]\n\n## Proof of Concept\n[Minimal working request or script]\n\n## Impact\n[What the attacker can achieve]\n\n## Affected Version\n[Version, commit, or deployment target tested]\n```\n\n## Quality Gate\n\nBefore submitting:\n\n- The code path is reachable from a real user or network boundary\n- The input is genuinely user-controlled\n- The sink is meaningful and exploitable\n- The PoC works\n- The issue is not already covered by an advisory, CVE, or open ticket\n- The target is actually in scope for the bounty program\n",{"name":5,"version":24,"metadata":25,"description":7},"1.0.0",{"origin":26},"ECC direct-port adaptation","main","a73152352c0612252131e5cf84e91312a6cf17dc","utilities\u002Fsecurity-bounty-hunter","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill security-bounty-hunter",{"tool":41,"command":42},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill security-bounty-hunter",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill security-bounty-hunter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",true,[],[50,57,64,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CWQSMYY026W72ECJ59802E","regex-vs-llm-structured-text","Decision framework for choosing between regex and LLM when parsing structured text — start with regex, add LLM only for low-confidence edge cases.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fregex-vs-llm-structured-text\u002FSKILL.md",[],[]]