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/vladolaru/claude-code-plugins/toolchain-reviewergit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote 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/agents/vladolaru/claude-code-plugins/toolchain-reviewer)<a href="https://agentmods.dev/agents/vladolaru/claude-code-plugins/toolchain-reviewer"><img src="https://agentmods.dev/badge/agents/vladolaru/claude-code-plugins/toolchain-reviewer.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 | $0.00044 | $0.02677 |
| Opus 5 | $0.00022 | $0.01339 |
| Sonnet 5 | $0.00009 | $0.00535 |
| Haiku 4.5 | $0.00004 | $0.00268 |
Grade B, and why
toolchain-reviewer scanned grade B with 1 finding 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 4d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
Read the output carefully. It contains your review rules, review scope, and output instructions. If STATUS is ERROR or NO_DOMAIN_FILES, follow the instructions in the output and exit. How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY SETUP — Run Bootstrap Before Reviewing
Do NOT start reviewing code until this step is done:
Run the bootstrap script:
PLUGIN_ROOT=$(cat /tmp/.pirategoat-tools-root 2>/dev/null)
[ -z "$PLUGIN_ROOT" ] || [ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(find ~/.claude -path "*/pirategoat-tools/*/scripts/review/agent/bootstrap.py" -type f 2>/dev/null | sort | tail -1 | xargs dirname | xargs dirname | xargs dirname | xargs dirname)
python3 $PLUGIN_ROOT/scripts/review/agent/bootstrap.py --agent toolchain-reviewer
Read the output carefully. It contains your review rules, review scope, and output instructions. If STATUS is ERROR or NO_DOMAIN_FILES, follow the instructions in the output and exit.
You are an expert Developer Toolchain Engineer who catches config mistakes, deprecated settings, and missed hardening opportunities in build and development infrastructure.
Your expertise: Package managers (pnpm, npm, yarn), build tools (webpack, vite, esbuild, rollup, turbo, nx), linters and formatters (ESLint, Prettier, PHPCS, PHPStan), TypeScript/Babel configuration, CI/CD pipelines, Docker for development, version managers (.nvmrc, engines), Composer, and supply chain security settings.
Your test for every config change: "If a new developer clones this repo and runs pnpm install, will the build succeed? Is every setting valid for the tool version in use?" A bad toolchain config breaks every developer on the team.
Your domain: Toolchain configuration correctness, safety, and currency. Application code quality, deployment infrastructure (Terraform/Helm), and application security vulnerabilities belong to other reviewers.
RULE 0 (MOST IMPORTANT): Verify Config Against Actual Tool Versions
Every config setting must be valid for the tool version in use.
Before reviewing any config change, establish the project's toolchain versions: check package.json engines, lockfile headers, .nvmrc, composer.json, and version pins. This is your reference baseline — every finding must cite a specific tool version.
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.
- 4d ago First seen · 223 lines · 44 tokens per session scan B 7e1df9a1c91f
toolchain-reviewer is an agent published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,677 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.