Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add woohyun212/security-skill --skill bug-bounty-validationgit clone --depth 1 https://github.com/woohyun212/security-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/woohyun212/security-skill/bug-bounty-validation)<a href="https://agentmods.dev/skills/woohyun212/security-skill/bug-bounty-validation"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/bug-bounty-validation.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.03130 |
| Opus 5 | $0.00015 | $0.01565 |
| Sonnet 5 | $0.00006 | $0.00626 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
bug-bounty-validation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
Provides a structured decision framework for validating bug bounty findings before submission. Runs a sequential gate system — 7-Question Gate, Always-Rejected List, Chain Requirement Evaluation, 4 Pre-Submission Gates, and CVSS 3.1 severity assessment — to produce a final verdict of SUBMIT, KILL, NEEDS CHAIN, or NEEDS IMPROVEMENT. Eliminates wasted submissions by catching invalid, out-of-scope, or low-quality reports before they reach the program.
When to use
- After discovering a potential vulnerability and before writing the full report
- When unsure whether a finding is worth submitting
- When a finding seems valid but impact is borderline
- When you have a low-severity finding and want to know if chaining elevates it
- When a triage response came back "Informational" or "N/A" and you want to understand why
- When reviewing a draft report for quality before final submission
Prerequisites
- A potential finding with at least one HTTP request/response pair demonstrating the behavior
- Knowledge of the target program's scope page (assets, exclusions, accepted vulnerability classes)
- Access to the program's policy page on HackerOne, Bugcrowd, Intigriti, or equivalent platform
- No external tools are required — this skill is a decision framework
Inputs
| Variable | Required | Description |
|---|---|---|
BV_FINDING |
Yes | Short description of the vulnerability (e.g., "IDOR on /api/orders/ID allows reading other users' orders") |
BV_ASSET |
Yes | Full domain or asset where the finding was observed (e.g., api.example.com) |
BV_VULN_CLASS |
Yes | Vulnerability class (e.g., IDOR, XSS, SSRF, Open Redirect, CSRF) |
BV_POC_STEPS |
Yes | Number of reproduction steps documented |
BV_IMPACT |
Yes | One sentence describing the concrete business impact |
BV_AUTH_REQUIRED |
Yes | none, user, or admin — minimum privilege level required to exploit |
BV_PROGRAM_SCOPE_URL |
Optional | URL to the program's scope page for cross-reference |
BV_CHAIN_PARTNER |
Optional | Second vulnerability you can chain with this finding (leave blank if standalone) |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 252 lines · 31 tokens per session scan A f3d3877cffcc
bug-bounty-validation is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 3,130 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…