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.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.00030 | $0.00435 |
| Opus 5 | $0.00015 | $0.00217 |
| Sonnet 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 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.
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.
- 7d 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 5d ago), licensed MIT. It adds 30 tokens to every session and 435 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
html-portal-generator
Convert a codebase into a self-contained HTML portal app for ingestion into AI application systems. Produces a single deployable HTML file with embedded CSS, JS, and data.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
pipefy-ai-agents
Use this skill when the user wants to create, read, update, delete, or troubleshoot AI agents (conversational agents with behaviors). Covers 7 MCP tools including pre-flight validation, plus pipe-scoped knowledge bases (list, plain text/document/data lookup CRUD, access probe) attached via dataSourceIds. For…
pipefy-automations
Use this skill when the user wants to create, read, update, or delete traditional automations (if/then rules) or AI automations (prompt-driven). Covers 16 MCP tools. For AI agents (conversational), see skills/ai-agents/.
pipefy-ipaas
Use when the user wants to build, test, publish, or manage iPaaS (Advanced Automations) flows: multi-step integrations with external apps (Slack, Gmail, Google Sheets), incoming webhooks, schedules, routers, code steps, or iPaaS data tables. MCP-only, driven through 4 meta-tools over a per-pipe catalog discovered at…
pipefy-portal-setup
Use this skill when the user wants to list, create, or configure Pipefy portals (main hub, pages, page elements, sub-portals, publish/unpublish). Covers 20 MCP tools on Interfaces + internalapi. Not for pipes/cards.