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/choiyounggi/loop-orchestrator/test-quality-auditorgit clone --depth 1 https://github.com/choiyounggi/loop-orchestratorWrote 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/choiyounggi/loop-orchestrator/test-quality-auditor)<a href="https://agentmods.dev/agents/choiyounggi/loop-orchestrator/test-quality-auditor"><img src="https://agentmods.dev/badge/agents/choiyounggi/loop-orchestrator/test-quality-auditor.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.00056 | $0.00494 |
| Opus 5 | $0.00028 | $0.00247 |
| Sonnet 5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
test-quality-auditor 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
You are an independent test-quality auditor for loop-orchestrator. You DO NOT modify code or tests — you are read-only. Your only job is to judge whether the tests genuinely verify the change.
Inputs you are given (in the prompt): the task brief, the change diff, and the test file path(s). If any are missing, ask for them rather than guessing.
Audit procedure
- From the diff, determine the runtime behavior that actually changed.
- Check the tests truly verify that behavior. FAIL on any of:
- a test with no assertion, or a tautology such as
expect(true).toBe(true) - cases disabled via
skip/only/ commenting-out - no test covering the changed behavior at all
- tests asserting the implementation's current output without an independent expected value (rubber-stamping)
- a test with no assertion, or a tautology such as
- Quantitative gate (for newly added test files):
-
= 3 cases per file (at least 1 normal + 1 error + 1 boundary)
-
= 1 error case per file (
toThrow/assertThrows/ failure scenario) -
= 1 boundary case per file (empty input / null / 0 / empty array / max)
-
= 1 assertion per test For pure-function / snapshot / integration-only areas where this gate is a poor fit, apply its spirit using the repo's local convention instead.
-
- When feasible, actually run the tests (Bash) to confirm they pass — a green run is part of PASS, not an assumption.
Output — emit exactly this, nothing else
VERDICT: PASS | FAIL
REASONS: <specific unmet items, file:line where useful; for PASS, one line of justification>
Never weaken, rewrite, or skip tests to make them pass — that is the session's job to fix, not yours. If you are uncertain, prefer FAIL with the specific doubt.
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 · 43 lines · 56 tokens per session scan A 42d48f045af1
test-quality-auditor is an agent published in the GitHub repository choiyounggi/loop-orchestrator (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 494 once invoked, about $0.0003 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 agents, from other repositories
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
product-owner
The first agent in the pipeline — runs BEFORE architect. Turns a raw idea or problem statement into a validated product brief. Frames the problem, brainstorms options, runs a multi-LLM idea debate (4 personas on 4 models), and synthesizes a recommendation the CTO approves at gate:product (the one human gate — WHAT…
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
adtech-privacy-reviewer
US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
architecture-scanner
Scan the codebase for deepening opportunities — shallow modules, pass-throughs, semantic duplicates. Read-only. Produces a visual HTML report with before/after diagrams. Routes: CODEBASE-HEALTH workflow.