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/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/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/choiyounggi/loop-orchestrator/test-quality-auditor"><img src="https://agentmods.dev/badge/agents/choiyounggi/loop-orchestrator/test-quality-auditor.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.00056 | $0.00494 |
| Opus 5.5 | $0.00022 | $0.00198 |
| Sonnet 5.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 2mo 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.
- 2mo 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 3mo ago), licensed MIT. It adds 56 tokens to every session and 494 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-08-31.
Other agents, from other repositories
ai-eval-engineer
Builds and maintains the eval pipeline for ai-system / agent-product archetypes. Outputs tests/eval/EVAL-.md files (golden citation, refuse-when-uncertain, output schema, prompt injection, cost-overrun, cross-user isolation). Runs regression on every prompt or model change. Detects drift.
qa-executor
Run an approved QA test plan against a built harness, assert every observation point, produce a report with per-scenario evidence, and emit bug candidates. Never edits test or product code to make a run pass.
mobile-app-builder
React Native implementer for Product-Builder products whose users work in the field (home-services dispatch, construction field-docs, field-booking, delivery). Builds the mobile app to the design-advisor's RN contract with TDD — offline-first sync, camera/photo + location capture, push notifications, and…
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
e2e-test-engineer
Use after qa-engineer passes and before/around devops deploy. Generates Playwright golden-path E2E specs (auth → create → pay) for the shipped product, then replays them against the LIVE URL as the post-deploy gate — replacing infra-provisioner's 3-ping smoke check with real user-journey proof.
ai-prompt-architect
Designs and versions LLM system prompts for ai-system / agent-product archetypes. Outputs docs/adr/ADR-{NN}-PROMPT-{name}.md files with sha256-pinned prompt text, jailbreak resistance test cases, and revision history. Pairs with ai-eval-engineer for golden-set scenarios.