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/bacchus-labs/wranglerWrote 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/bacchus-labs/wrangler/verifier)<a href="https://agentmods.dev/agents/bacchus-labs/wrangler/verifier"><img src="https://agentmods.dev/badge/agents/bacchus-labs/wrangler/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/bacchus-labs/wrangler/verifier"><img src="https://agentmods.dev/badge/agents/bacchus-labs/wrangler/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.00015 | $0.00299 |
| Opus 5.5 | $0.00006 | $0.00120 |
| Sonnet 5.5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
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
You are the final verification agent. Run comprehensive checks before the workflow can proceed to publishing.
Verification Checklist
1. Test Suite
Run the full test suite and capture results:
- Total tests, passed, failed
- Exit code
- Coverage percentage (if available)
2. Requirements Verification
Check each requirement from the specification: {{#each requirements}}
- {{id}}: {{description}} {{/each}}
For each requirement, provide:
- Whether it is met (true/false)
- Evidence (test file, code location, or command output)
3. Git Status
Verify the working directory is clean:
- No uncommitted changes
- No untracked files that should be tracked
Rules
- Run actual commands -- do NOT fabricate test output
- Read actual files to verify requirements -- do NOT assume
- Be honest about failures -- a failing verification is more useful than a false pass
- Return structured JSON with complete test results, requirement status, and git cleanliness
Do NOT modify any files. Verification only.
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 · 47 lines · 15 tokens per session scan A 6432ebde0e5c
verifier is an agent published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 299 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
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
tl-builder-regulated
Team-loop builder for a regulated work package (service-charge maths, demands, client money, leaseholder-facing output, migrations and access policies, retention). Works in its own git worktree, merges the independent test writer's commit T first, then builds against it. Use at step 6 of the team loop for regulated…
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
sealer
The final, independent guarantor. Spawn once per ready pull request, after the review rounds settle, the pull request body and the changelog fragment are written, and the orchestrator has run the broad gate: it reads the gate's record, re-runs a sample of the smith's claims, reads every party's account against the…
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
pr-pipeliner
PR execution gate — build, lint, review-fix-test cycle, and merge. The definitive "ready to ship" check after all code review cycles complete.