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 NeuroGhostDev/booster_mcp --skill booster-feature-addgit 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-feature-add)<a href="https://agentmods.dev/skills/neuroghostdev/booster_mcp/booster-feature-add"><img src="https://agentmods.dev/badge/skills/neuroghostdev/booster_mcp/booster-feature-add/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/neuroghostdev/booster_mcp/booster-feature-add"><img src="https://agentmods.dev/badge/skills/neuroghostdev/booster_mcp/booster-feature-add.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.00435 |
| Opus 5.5 | $0.00012 | $0.00174 |
| Sonnet 5.5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
booster-feature-add 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 1mo 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 Feature Add
Цель
Перед реализацией найти правильное место, стиль и аналог существующей фичи.
Алгоритм
project_memory("get", "architecture_overview", repo="<repo>")
project_memory_recall(query="<feature description>", repo="<repo>")
preflight_analysis(task="<feature description>", target="<suspected symbol>", repo="<repo>")
semantic_search("<feature description>")
find_symbol("<related class or service>")
impact_analysis(target="<related class or service>", repo="<repo>", max_depth=3)
read_with_context("<analog file>", line=<line>, context=60)
call_graph("<neighbor symbol>")
import_graph("<target file>")
git_intelligence(symbol="<related class or service>", repo="<repo>", limit=8)
external_deps("<neighbor symbol>")
find_duplicates(min_lines=3)
До написания кода выясни
- куда добавлять реализацию
- есть ли аналог или шаблон
- какие зависимости уже используются
- нужен ли тест и конфиг
- какие diagnostics уже есть в затронутых файлах
- какой blast radius у основного символа
После реализации
find_symbol("<new symbol>")
collect_diagnostics(paths=["<changed file>"], repo="<repo>")
validation_loop_plan(task="<feature description>", changed_paths=["<changed file>"], repo="<repo>")
run_validation_checks(commands=["<project tests>"], paths=["<changed file>"], repo="<repo>")
booster.task_complete(task_id="<task-id>", repo_paths=["<repo>"])
project_memory("set", "feature_<name>", "...", repo="<repo>")
remember_project_fact(category="feature", fact="<what changed and why>", repo="<repo>")
booster.task_complete() is the lifecycle boundary for the agent task. It
queues a final bounded reindex and preserves the generated artifacts in an
immutable snapshot keyed by the current git commit and artifact digest.
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.
- 1mo ago First seen · 54 lines · 30 tokens per session scan A 776db47a918d
booster-feature-add is a skill published in the GitHub repository NeuroGhostDev/booster_mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 435 once invoked, about $0.0001 per session on Opus 5.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
capabilities-manager
Manage capa CLI configuration — capabilities.yaml / capabilities.json, skills, MCP servers, tools, hooks, sub-agents, rules, plugins, AGENTS.md / CLAUDE.md, security options, tool exposure modes, capa wrap shadow workspaces, --passthrough native writes, registries (including Claude marketplaces), activity traces, and…
bootstrap
Capify an existing project. Scans the repo for already-installed MCP servers, skills, rules, hooks, sub-agents, and plugins (across .claude, .cursor, .codex, .gemini, etc.), consolidates them into shared top-level directories (skills/, rules/, hooks/), and synthesizes a sound capabilities.yaml from the inventory. Use…
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
acceptance-test-authoring
Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
gherkin-authoring
Use when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data Tables, tags, or Gherkin embedded in Markdown.