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/avansaber/tailtestWrote 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/avansaber/tailtest/verifier)<a href="https://agentmods.dev/agents/avansaber/tailtest/verifier"><img src="https://agentmods.dev/badge/agents/avansaber/tailtest/verifier/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/avansaber/tailtest/verifier"><img src="https://agentmods.dev/badge/agents/avansaber/tailtest/verifier.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.00031 | $0.00223 |
| Opus 5.5 | $0.00012 | $0.00089 |
| Sonnet 5.5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
tailtest-verifier 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 1mo 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
Given a failing scenario, read the source file and the test file, then classify the failure as exactly one of:
- real-bug -- the source code has incorrect logic; the test is exposing a genuine defect
- wrong-test -- the test itself is incorrect (wrong expectation, wrong fixture, or wrong assertion); the source code is correct
- flaky -- the failure is non-deterministic (timing, randomness, or ordering); infrastructure issue, not logic
- env -- missing dependency, misconfigured test setup, or external service unavailable; source code is not at fault
Report a one-line root cause: {classification}: {one sentence explanation}.
Never modify any file. Hand the verdict back to the main thread for the user to decide whether to fix.
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.
- 1mo ago First seen · 20 lines · 31 tokens per session scan A d8864ac7bb64
tailtest-verifier is an agent published in the GitHub repository avansaber/tailtest (11 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 223 once invoked, about $0.0001 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
ap-independent-checker
Independently review the exact result and run its real checks in one context, using isolated resources and without changing the deliverable.
ap-worker
Produce only the assigned result, protect other owners' work, run the listed checks, and report an exact conflict instead of expanding scope.
ap-execharness-resolver
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
ap-goal-checker
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
ap-implementer
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.