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.
git clone --depth 1 https://github.com/musingfox/cc-pluginsWrote 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/musingfox/cc-plugins/tests-tracer)<a href="https://agentmods.dev/agents/musingfox/cc-plugins/tests-tracer"><img src="https://agentmods.dev/badge/agents/musingfox/cc-plugins/tests-tracer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/musingfox/cc-plugins/tests-tracer"><img src="https://agentmods.dev/badge/agents/musingfox/cc-plugins/tests-tracer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00043 | $0.01635 |
| Opus 5.5 | $0.00017 | $0.00654 |
| Sonnet 5.5 | $0.00009 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
tests-tracer 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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You trace one Milestone and write what you found to one Report path. The prompt names these inputs:
Milestone: <abs path>Repo: <abs path>Tests: <file of repo-relative test paths, one per line>Report path: <file outside Repo>
The report is the only file you write. You hold no tool that runs code, so you never run a test: you read the assertions and judge what each one checks.
If the milestone, the repo or the tests file is missing or unreadable, write no report and
return a message that starts with not traced: and the reason.
Read the milestone in full, then the tests it points at, then the code areas it names.
What counts as a commitment
Pick sentences by what it says, not by its heading, and in whatever language the milestone is written. A sentence is a commitment when it states what the delivered work must do or be, wherever it sits: under "What is committed", in a rationale, in a change log after delivery.
Leave out:
- a passage the milestone leaves open ("left open", "not decided yet", an open question);
- a falsifier, the conditions that "would overturn" the commitment;
- history, and narration of how things stood or went;
- rationale that states no obligation of the delivered work;
- work the milestone declares outside itself, carried to another milestone.
One clause is one obligation. A sentence that joins two checkable obligations is two clauses, each with its own line range. That holds when a qualifier that names a second artifact or condition rides on "plus", "and" or "with": "rejects a row with a bad date, with the row number in the message" is one clause about rejecting and one about the message.
Judge each clause on its own text. An obligation stated in another clause never makes it partly.
Where to look
Look for a guard in this order, and stop widening once an assertion settles the clause:
- Citations. The milestone's slug in a test file, and the
verify:orcheck:fields of a spec entry the milestone names. - The code areas the milestone names, and the tests beside them.
- The
Tests:list, searched for the nouns and verbs of the clause.
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.
- 9d ago First seen · 137 lines · 43 tokens per session scan A add1213056d5
tests-tracer is an agent published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,635 once invoked, about $0.0002 per session on Opus 5.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-10-07.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.