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-mcp-workflowgit 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-mcp-workflow)<a href="https://agentmods.dev/skills/neuroghostdev/booster_mcp/booster-mcp-workflow"><img src="https://agentmods.dev/badge/skills/neuroghostdev/booster_mcp/booster-mcp-workflow/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-mcp-workflow"><img src="https://agentmods.dev/badge/skills/neuroghostdev/booster_mcp/booster-mcp-workflow.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.00052 | $0.01179 |
| Opus 5.5 | $0.00021 | $0.00472 |
| Sonnet 5.5 | $0.00010 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
booster-mcp-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Booster MCP Workflow
Цель
Безопасно подключить репозиторий к Booster MCP, получить актуальный контекст и убедиться, что артефакты анализа доступны агенту.
Базовый Цикл
- Проверь встроенные навыки через
list_agent_skills(). - Для нового или большого локального репозитория сначала запусти из его корня
booster expand --profile balanced. Это создаёт ограниченный scope и не загружает embedding-модель. - Прочитай
.agents/booster/scan_report.json. Если достигнуты limits, реши осознанно: сохранить быстрый scope или повторитьbooster expand --profile deepперед индексацией. - Добавь проект:
add_repo("<absolute_repo_path>"). MCP использует сохранённыйscan_config.jsonи возвращаетjob_id. - Проверь job через
index_status(job_id="..."); для bounded ожидания используйwait_until_ready(), а не долгий MCP request. - Проверь результаты индексации и пути к артефактам:
repo_stats()иget_repo_artifacts(). - Получи сжатую структуру проекта:
inject_context()илиget_repo_map(). - Для известных символов, API и mixed-запросов используй
hybrid_search(); для чисто смыслового поиска используйsemantic_search(). - При необходимости получи рекомендации по актуальной документации:
fetch_stack_docs(). - Выбери специализированный skill для дальнейшей работы.
- Перед финальным ответом вызови
booster.task_complete(task_id="<task-id>"): Booster поставит финальный reindex и сохранит commit-bound snapshot.
booster expand --profile balanced
add_repo("D:\\workSpace\\project")
index_status(repo_path="D:\\workSpace\\project")
get_repo_artifacts()
inject_context(include_map=True, include_stack=True, include_conventions=True)
repo_stats()
hybrid_search("authenticate_user JWT")
fetch_stack_docs()
booster.task_complete(task_id="task-123")
Проверка Артефактов
get_repo_artifacts() возвращает состояние канонических файлов:
.agents/booster/repo_map.md.agents/booster/repo_map_architecture.md.agents/booster/repo_map_symbols.md.agents/booster/index_health.json.agents/booster/code_city.html.agents/booster/scan_config.json.agents/booster/scan_report.json.agents/booster/latest.json.agents/booster/snapshots/<commit>-<state>-<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 · 90 lines · 52 tokens per session scan A 59acab282f0f
booster-mcp-workflow is a skill published in the GitHub repository NeuroGhostDev/booster_mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 1,179 once invoked, about $0.0002 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.