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 agents/bug-ops/mcp-execution/rust-code-reviewergit clone --depth 1 https://github.com/bug-ops/mcp-executionWhat 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 | $0.00019 | $0.01490 |
| Opus 5 | $0.00010 | $0.00745 |
| Sonnet 5 | $0.00004 | $0.00298 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
rust-code-reviewer 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 yesterday.
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 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.
- yesterday First seen · 255 lines · 19 tokens per session scan A b3cb5fa3d961
rust-code-reviewer is an agent published in the GitHub repository bug-ops/mcp-execution (46 stars, last pushed 7d ago), with no licence file. It adds 19 tokens to every session and 1,490 once invoked, about $0.0001 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-30.
Other agents, from other repositories
lint-fix
Use when user asks to lint / format / clean up code style across any project. Triggers (RU + EN) — "причеши код", "lint fix", "отформатируй", "format code", "прогон линтера", "fix lint", "поправь линт", "format", "lint", "ruff fix", "eslint fix", "ktlint", "fix style". Auto-detects language from project path or…
test-runner
Use when user asks to run tests for any project — Python (pytest), TypeScript (next/jest), or Kotlin (gradlew test). Triggers (RU + EN) — "прогон тестов", "прогони тесты", "run tests", "test ", "тесты ", "пройдут ли тесты", "прогон тестов перед деплоем", "smart test", "тестируй", "проверь тесты". Use proactively…
memory-keeper
Use at end of significant Claude Code session to capture session outcomes into MEMORY-LOG.md. Triggers (RU + EN) — "зафиксируй сессию", "сохрани память", "обнови память", "записать сессию", "save session memory", "log this session", "checkpoint memory". Use proactively after completing major work — refactor, deploy…
vault-audit
Use when user asks to audit knowledge vault — find orphan notes (not in INDEX), broken wiki-links, stale references, or check vault hygiene. Triggers (RU + EN) — "причеши vault", "audit vault", "audit knowledge", "найди orphan заметки", "проверь knowledge", "почисти vault", "найди битые ссылки". Use proactively after…
daily-report
Use when user asks for a summary of work done today/yesterday or weekly. Triggers (RU + EN) — "что вчера сделал", "что сегодня было", "daily report", "standup", "отчёт за день", "отчёт за неделю", "weekly report", "что в работе", "summary дня". Aggregates git logs across all repos in workspace, uncommitted changes…
overview
How Serpentine's structured CLI output gives AI coding agents precise structural context before they read a single file.