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/theagenticguy/opencodehub/doc-reference-mcp-toolsgit clone --depth 1 https://github.com/theagenticguy/opencodehubWhat 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.00000 | $0.01511 |
| Opus 5 | $0.00000 | $0.00756 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
doc-reference-mcp-tools 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packet · {{ repo }} · reference/mcp-tools.md
1. Objective
Produce {{ docs_root }}/reference/mcp-tools.md: the authoritative reference for every MCP tool {{ repo }} exposes, one H2 per tool, each with a verbatim signature, input/output shapes, a one-sentence purpose, and a path:LOC citation to the handler file.
2. Scope
- Create:
{{ docs_root }}/reference/mcp-tools.md - Do not touch:
{{ docs_root }}/reference/public-api.md,{{ docs_root }}/reference/cli.md, or any other file under{{ docs_root }}/, any source file in the repo,.context.md,.prefetch.md, or any.packets/*.mdother than this one. - Conditional file — this packet is only seeded when
{{ repo }}contains an MCP server package (the orchestrator verifiedproject_profile.stacksincludes"MCP"ortool_mapis non-empty before spawning).
3. Input specification
| Source | Read how | Cache state |
|---|---|---|
| Shared context | Read {{ context_path }} |
always first |
| Prefetch ledger | Read {{ prefetch_path }} |
always first |
| MCP tool inventory | {{ prefetch_path }} § tool_map |
cached |
| Tool handler nodes | mcp__codehub__sql({query: "SELECT name, file_path, start_line FROM nodes WHERE kind='Function' AND file_path LIKE '%mcp%'"}) |
mid-run, only if tool_map slice is truncated |
| Verbatim signatures | Read <file_path>:<start_line> (signatures are not stored in the graph) |
mid-run |
| Usage count per tool | mcp__codehub__context({symbol: <tool-handler>}) |
mid-run |
4. Process
Read {{ context_path }}andRead {{ prefetch_path }}. Confirm thetool_mapdigest is present and non-empty; if empty, follow Fallback paths.- Build the tool roster from
{{ prefetch_path }} § tool_map: tool name, handlerfile_path:start_line, input/output schema digest. - For each tool in the roster:
Readthe handler file atstart_line..start_line+30and extract the exact signature (function or registration block). Do not paraphrase. - For each tool: pull a one-sentence purpose from the registration description (the MCP
describestring); if missing, infer from the handler docstring and mark the inference in the Work log. - Draft
reference/mcp-tools.md: H1 ={{ repo }} · MCP tools, one H2 per tool in alphabetical order. Each H2 contains the verbatim signature fenced as code, a one-sentence purpose, an input/output shape summary, and apath:LOCcitation. Write {{ docs_root }}/reference/mcp-tools.md.
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 · 101 lines · 0 tokens per session scan A 73d21474ef98
doc-reference-mcp-tools is an agent published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,511 tokens. 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.