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/zach-source/mcp-rust-proxy/mcp-proxy-quality-reportgit clone --depth 1 https://github.com/zach-source/mcp-rust-proxyWrote 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/zach-source/mcp-rust-proxy/mcp-proxy-quality-report)<a href="https://agentmods.dev/commands/zach-source/mcp-rust-proxy/mcp-proxy-quality-report"><img src="https://agentmods.dev/badge/commands/zach-source/mcp-rust-proxy/mcp-proxy-quality-report.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.00009 | $0.00143 |
| Opus 5 | $0.00005 | $0.00072 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
mcp-proxy-quality-report 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.
What it actually says
Generate a quality report showing context performance metrics.
Instructions for Claude:
- Read trace://quality/recent-feedback resource
- Read trace://quality/top-contexts resource (when available)
- Read trace://quality/deprecated-contexts resource (when available)
- Query the database for aggregate statistics
- Present a formatted report showing:
- Recent feedback trends (scores over time)
- Top performing contexts (high scores)
- Contexts needing review (low scores)
- Recommendations for improvement
- Suggest which contexts to update or deprecate
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 · 19 lines · 9 tokens per session scan A 65c5d68ea2bd
mcp-proxy-quality-report is a command published in the GitHub repository zach-source/mcp-rust-proxy (5 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 143 once invoked, about $0.0000 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 commands, from other repositories
activity
Analyze recent external (non-test) activity on the Strale platform — calls, signups, x402 — and produce a short synthesis.
review
Perform a comprehensive code review with actionable feedback.
test
Generate tests for the specified code or feature.
git-workflow
You are executing the provardx-cli development git workflow. Follow these steps in order. Stop and confirm with the user at each CONFIRM point before proceeding.
judge
Evaluate the execution quality of a skill or agent.
against
Side-by-side delta between two scorecards of the same skill.