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/yaleh/meta-cc/meta-errorsgit clone --depth 1 https://github.com/yaleh/meta-ccWhat 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.00010 | $0.00071 |
| Opus 5 | $0.00005 | $0.00036 |
| Sonnet 5 | $0.00002 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
meta-errors 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- meta-errors — 100% identical, 0 lines differ
What it actually says
Meta Errors Capability
This capability analyzes error patterns in your workflow.
Usage
/meta-errors
Features
- Error pattern detection
- Prevention recommendations
- Context analysis
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.
- 2d ago First seen · 23 lines · 10 tokens per session scan A 38cb3e1b3fa0
meta-errors is a command published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 11d ago), licensed MIT. It adds 10 tokens to every session and 71 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-08-30.
Other commands, from other repositories
gcroot
Displays information about references (or roots) to a specified object. It helps in identifying what is keeping an object alive in the managed heap.
clrstack
Displays managed call stacks for all threads or a specific thread.
dumpheap
Analyzes managed heap objects, identifies memory leaks, and traces object references.
dumpstack
Helps examine thread call stacks. While clrstack is more commonly used for managed call stacks, dumpstack can also be used to inspect stack frames, including native ones.
printexception
Prints information about an exception object.
dumpassembly
Command "dumpassembly" from frankbolero/dotnet-dump-mcp, covering dumpassembly, usage and clrmd implementation.