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 commands/clchinkc/document-mcp/1-researchgit clone --depth 1 https://github.com/clchinkc/document-mcpWrote 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/clchinkc/document-mcp/1-research)<a href="https://agentmods.dev/commands/clchinkc/document-mcp/1-research"><img src="https://agentmods.dev/badge/commands/clchinkc/document-mcp/1-research.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.00000 | $0.00093 |
| Opus 5 | $0.00000 | $0.00046 |
| Sonnet 5 | $0.00000 | $0.00019 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
1-research 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 3d 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
Research (Multi-Agent Parallel)
Implementation Analysis: Examine all implementation files (src/) for fundamental principles, concrete patterns, and system design. Focus on complexity vs. usefulness vs. extensibility trade-offs, architectural decisions, and code quality patterns.
Testing Analysis: Review all test files (tests/) for testing purpose, pass/fail conditions, coverage gaps, and effectiveness. Optimize testing strategy to ensure implementation correctness with minimal resource usage and maximum reliability.
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.
- 3d ago First seen · 5 lines · 0 tokens per session scan A 317f9ded6d18
1-research is a command published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 93 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 commands, from other repositories
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.
git
Git operations with intelligent commit messages and workflow optimization.
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.