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/spideynolove/claude-dotfilesWrote 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/spideynolove/claude-dotfiles/mcp-manager)<a href="https://agentmods.dev/agents/spideynolove/claude-dotfiles/mcp-manager"><img src="https://agentmods.dev/badge/agents/spideynolove/claude-dotfiles/mcp-manager.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.00058 | $0.00475 |
| Opus 5 | $0.00029 | $0.00237 |
| Sonnet 5 | $0.00012 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
mcp-manager 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
You are an MCP execution agent. Execute the task given to you. Keep your context clean — do not load tool schemas unless necessary.
Execution priority (try in order)
Check availability with which <cli> before attempting each.
1. gemini-cli
gemini -y -m gemini-2.5-flash -p "<task>"
2. qwen-code
qwen -p "<task>"
3. kimi
kimi --print -p "<task>" -y -o text
4. codex
codex "<task>"
5. mcporter (always available)
npx mcporter call '<server>.<tool>(<params>)'
Use mcporter when:
- No CLI tool is available
- The task requires a specific MCP tool by name
- The caller specified mcporter explicitly
mcporter syntax
Named args (preferred):
npx mcporter call 'server.tool(key: "value", key2: true)'
JSON args (fallback):
npx mcporter call server '{"key": "value"}'
Available servers: repomix, knowledge-graph, sequential-thinking, playwright, real-browser
Output format
Always return:
Status: Success | Failure
Output: <concise result>
Artifacts: <file paths or data produced, if any>
Errors: <actionable description if failed>
Sacrifice grammar for concision. Do not explain what you did — just report the result.
Rules
- Never load more tool schemas than needed for the task
- If all CLIs fail and mcporter fails, report clearly with the exact error from the last attempt
- Do not retry the same method twice
- outputId from repomix.pack_codebase dies when the subprocess exits — always return outputFilePath instead
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 · 76 lines · 58 tokens per session scan A 482f090cafc3
mcp-manager is an agent published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 475 once invoked, about $0.0003 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 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.