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.
git clone --depth 1 https://github.com/activeing123/mcptoonWrote 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/commands/activeing123/mcptoon/mcptoon-setup)<a href="https://agentmods.dev/commands/activeing123/mcptoon/mcptoon-setup"><img src="https://agentmods.dev/badge/commands/activeing123/mcptoon/mcptoon-setup/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/commands/activeing123/mcptoon/mcptoon-setup"><img src="https://agentmods.dev/badge/commands/activeing123/mcptoon/mcptoon-setup.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.00019 | $0.00299 |
| Opus 5 | $0.00010 | $0.00150 |
| Sonnet 5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
mcptoon-setup 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 today.
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
mcptoon setup
Help the user set up mcptoon by executing these steps yourself (do not ask the user to run commands) and reporting the real outputs:
- Check Python:
python --version(needs >= 3.10). If missing, tell the user to install Python from python.org and stop there. - Install/upgrade:
python -m pip install --upgrade mcptoon. It is a zero-dependency 128KB wheel — if it pulls in third-party packages, something is wrong; report it. - Verify:
mcptoon --version, thenmcptoon doctorfor config and connectivity status. Paste a short summary of the doctor output. - Show the win: run
mcptoon manifest --compact --tokensand report the tool count and token figure it prints for the user's own configuration. - Explain the bridge: the plugin's
.mcp.jsonstartsmcptoon servefor Claude Code automatically. If the MCP server list shows mcptoon as failed right after the very first install, restart the session once so the newly installed CLI is on PATH.
If anything fails, show the exact error and suggest the next step — never leave the user with a bare traceback.
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.
- today First seen · 26 lines · 19 tokens per session scan A 45c5b3736623
mcptoon-setup is a command published in the GitHub repository activeing123/mcptoon (195 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 299 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-09-08.
Other commands, from other repositories
axon-deploy
Deploy or restart the axon stack (qdrant, tei, chrome, axon) via docker compose.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.