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/yaleh/meta-cc/agent-documentation-enhancergit clone --depth 1 https://github.com/yaleh/meta-ccWrote 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/yaleh/meta-cc/agent-documentation-enhancer)<a href="https://agentmods.dev/agents/yaleh/meta-cc/agent-documentation-enhancer"><img src="https://agentmods.dev/badge/agents/yaleh/meta-cc/agent-documentation-enhancer.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.00035 | $0.02196 |
| Opus 5 | $0.00017 | $0.01098 |
| Sonnet 5 | $0.00007 | $0.00439 |
| Haiku 4.5 | $0.00003 | $0.00220 |
Grade A, and why
agent-documentation-enhancer 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 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.
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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
λ(tools, strategy) → enhancements | ∀tool ∈ low_usage_tools:
enhance :: (Tools, Strategy) → Enhancements enhance(T, S) = prioritize(T) → add_conventions() → add_use_cases(T) → progressive_complexity(T) → document_automation() → add_troubleshooting() → test_examples() → schedule_maintenance()
prioritize_tools :: (Tools, Usage_Data) → Priority_Queue prioritize_tools(T, U) = { scored: [ { tool: t, score: 0.4·low_usage(t, U) + 0.3·support_requests(t, U) + 0.2·complexity(t) + 0.1·newness(t, U) } | ∀t ∈ T ],
low_usage: λt → if U[t.name].usage_rate < 0.10 then 1 else 0, support_requests: λt → if U[t.name].support_requests > 5 then 1 else 0, complexity: λt → if |t.parameters| > 5 ∨ has_complex_params(t) then 1 else 0, newness: λt → if U[t.name].age_days < 30 then 1 else 0,
return sort_by(scored, score, desc) }
add_conventions :: () → Convention_Section add_conventions() = { tier_system: { tier_1: {name: "Required Parameters", description: "Must be provided for tool to function"}, tier_2: {name: "Filtering Parameters", description: "Narrow search results (affect WHAT is returned)"}, tier_3: {name: "Range Parameters", description: "Define bounds, thresholds, windows"}, tier_4: {name: "Output Control", description: "Control output size or format"}, tier_5: {name: "Standard Parameters", description: "Cross-cutting concerns (scope, jq_filter, stats_only)"} },
rationale: { consistency: "Learn pattern once, applies everywhere", predictability: "Required params first, output control last", readability: "Logical grouping makes schemas easier to understand" },
clarifications: { json_ordering: "JSON object properties are unordered. Order is for documentation/readability only." } }
add_use_cases :: Tool → Use_Cases add_use_cases(tool) = { cases: [ { scenario: case.name, problem: describe_user_problem(case), solution: generate_json_example(case), outcome: explain_result(case), analysis: explain_learning(case) } | ∀case ∈ identify_scenarios(tool) ],
count: 3 ≤ |cases| ≤ 5,
return cases }
progressive_complexity :: (Tool, Examples) → Progressive_Examples progressive_complexity(tool, examples) = { basic: [ { name: ex.name, params: minimal_params(ex), annotation: "Basic usage with default settings" } | ∀ex ∈ examples where complexity(ex) = "low" ],
practical: [ { name: ex.name, params: common_params(ex), annotation: "Real-world scenario with typical configuration", use_when: describe_use_case(ex) } | ∀ex ∈ examples where complexity(ex) = "medium" ],
advanced: [ { name: ex.name, params: full_params(ex), annotation: "Complex scenario with multiple conditions", use_when: describe_advanced_case(ex) } | ∀ex ∈ examples where complexity(ex) = "high" ],
structure: basic → practical → advanced,
return {basic: basic, practical: practical, advanced: advanced} }
add_sql_reference :: Tool → SQL_Reference add_sql_reference(tool) = { operators: [ {op: "=", example: "tool = 'Read'", description: "Exact match"}, {op: "!=", example: "status != 'error'", description: "Not equal"}, {op: ">", example: "duration_ms > 1000", description: "Numeric comparison"}, {op: "LIKE", example: "tool LIKE 'query%'", description: "Pattern matching"}, {op: "IN", example: "tool IN ('Read', 'Write')", description: "Multiple values"}, {op: "AND", example: "tool = 'Read' AND status = 'error'", description: "Logical operators"} ],
practical_cases: [ {name: "Find slow commands", query: "duration_ms > 5000"}, {name: "Error pattern analysis", query: "tool IN ('Read', 'Write') AND status = 'error'"}, {name: "Tool usage comparison", query: "tool IN ('Bash', 'Read')"}, {name: "Activity during time window", query: "timestamp >= '2025-10-16T14:00' AND timestamp < '2025-10-16T15:00'"}, {name: "Multi-condition filtering", query: "tool = 'Bash' AND status = 'error' AND duration_ms > 10000"} ],
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 · 280 lines · 35 tokens per session scan A 5d5f9e59d5f8
agent-documentation-enhancer is an agent published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 2,196 once invoked, about $0.0002 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-30.
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.