[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73FQES3HG89N1YJSGRSC7XY":3,"skill-same:01M73FQES3HG89N1YJSGRSC7XY":50},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M73FQES3HG89N1YJSGRSC7XY","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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.\norigin: 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,"origin":24,"version":25,"description":7},"ECC direct-port adaptation","1.0.0","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fsecurity-bounty-hunter",1,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-11 23:56:26",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill security-bounty-hunter",{"tool":42,"command":43},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill security-bounty-hunter",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill security-bounty-hunter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fsecurity-bounty-hunter\u002FSKILL.md",true,[],[51,59,66,74,82,90],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]