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 agentmods add skills/neuroghostdev/booster_mcp/booster-bug-huntnpx skills add NeuroGhostDev/booster_mcp --skill booster-bug-huntgit clone --depth 1 https://github.com/NeuroGhostDev/booster_mcpWrote 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/neuroghostdev/booster_mcp/booster-bug-hunt)<a href="https://agentmods.dev/skills/neuroghostdev/booster_mcp/booster-bug-hunt"><img src="https://agentmods.dev/badge/skills/neuroghostdev/booster_mcp/booster-bug-hunt.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.00043 | $0.00326 |
| Opus 5 | $0.00022 | $0.00163 |
| Sonnet 5 | $0.00009 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
booster-bug-hunt 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 5d 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.
What it actually says
booster Bug Hunt
Цель
Сузить поиск от симптома до конкретного символа, строки и причины.
Если есть stacktrace
analyze_error("<stacktrace>")
project_memory_recall(query="<stacktrace or symptom>")
flipchart_create_session("bug_<id>", ["<symbol1>", "<symbol2>"])
flipchart_call_graph("<symbol>", max_depth=4)
impact_analysis(target="<symbol>", max_depth=3)
read_with_context("<file>", line=<line>, context=25)
code_grep("<error fragment>")
git_diff("<file>")
git_intelligence(path="<file>", symbol="<symbol>", limit=10)
collect_diagnostics(paths=["<file>"])
Если есть только описание поведения
semantic_search("<symptom>")
find_symbol("<suspected symbol>")
preflight_analysis(task="<symptom>", target="<suspected symbol>")
flipchart_quick_debug("<symbol>", max_depth=4)
external_deps("<symbol>")
Проверки
- regression через git_diff и git_log
- regression через git_diff и git_intelligence
- diagnostics через collect_diagnostics до и после фикса
- внешний сервис через external_deps
- дубли логики через find_duplicates
Финал
Сохрани причину и фикс в project_memory и remember_project_fact.
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.
- 5d ago First seen · 50 lines · 43 tokens per session scan A 7b519a1f1dd3
booster-bug-hunt is a skill published in the GitHub repository NeuroGhostDev/booster_mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 326 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-31.
Other skills, from other repositories
debug-helper
Systematic debugging approach for identifying and fixing issues.
cel-debugging
Diagnosing and resolving Common Expression Language (CEL) compilation and evaluation errors.
unity-runtime-performance
Use for runtime performance triage from the project filesystem: quality tiers, graphics/URP-HDRP settings, lighting, large assets, scene complexity proxies, and build-size hotspots (no Editor Profiler required).
unity-broken-refs-triage
Use when prefabs/scenes show Missing Script or pink materials: triage broken script and asset GUID references and decide fix order.
unity-memory-asset-pressure
Use to find memory/disk pressure from assets: large files, textures, audio, video, ML models, and Addressables that should be remote.
bun-guides-runtime
Guides for runtime features: environment variables, timers, console logging, debugging, and crash handling in Bun.