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 elproximoframework/Skills_Ingenieria --skill bug-huntergit clone --depth 1 https://github.com/elproximoframework/Skills_IngenieriaWrote 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/elproximoframework/skills_ingenieria/bug-hunter)<a href="https://agentmods.dev/skills/elproximoframework/skills_ingenieria/bug-hunter"><img src="https://agentmods.dev/badge/skills/elproximoframework/skills_ingenieria/bug-hunter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/elproximoframework/skills_ingenieria/bug-hunter"><img src="https://agentmods.dev/badge/skills/elproximoframework/skills_ingenieria/bug-hunter.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01926 |
| Opus 5 | $0.00015 | $0.00963 |
| Sonnet 5 | $0.00006 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00193 |
Grade A, and why
bug-hunter 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 385 lines · 30 tokens per session scan A b3e9b84416d0
bug-hunter is a skill published in the GitHub repository elproximoframework/Skills_Ingenieria (2 stars, last pushed 2mo ago), with no licence file. It adds 30 tokens to every session and 1,926 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-09-03.
Other skills, from other repositories
qa-bug-root-cause-analysis
A method for finding the underlying causes of recurring or production bugs using approaches such as asking “why” repeatedly, cause-and-effect diagrams, and fishbone diagrams. It separates immediate, contributing, and system-level causes.
qa-bug-lifecycle
A guide to managing a bug from discovery through confirmation, assignment, fixing, retesting, and closure. It also defines special states such as rejected, postponed, and reopened.
qa-bug-reporting
A guide for writing bug reports that developers can reproduce and investigate. It covers setup, exact steps, expected and actual results, possible causes, impact, and supporting files.
qa-execution-observation
A structured way to observe software while tests run, including its visible results, API responses, logs, screens, data, performance, and outside services.
sentinel
QA artifact generator — point it at a PR or give it freeform instructions. Navigates the UI using agent-browser, captures screenshots at each step, and stitches a GIF. Flags: --debug (annotated overlays), --folder (custom artifact folder).
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.