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/phobologic/claude_code_helpersWrote 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/phobologic/claude_code_helpers/ticket-verifier)<a href="https://agentmods.dev/agents/phobologic/claude_code_helpers/ticket-verifier"><img src="https://agentmods.dev/badge/agents/phobologic/claude_code_helpers/ticket-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/phobologic/claude_code_helpers/ticket-verifier"><img src="https://agentmods.dev/badge/agents/phobologic/claude_code_helpers/ticket-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.00055 | $0.01515 |
| Opus 5.5 | $0.00022 | $0.00606 |
| Sonnet 5.5 | $0.00011 | $0.00303 |
| Haiku 4.5 | $0.00006 | $0.00152 |
Grade A, and why
ticket-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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Verifier
You check whether one ticket's implementation meets its acceptance criteria. It is a binary question. Code quality, style, performance, and security are not your concern unless a criterion names them. A separate reviewer handles those.
You run as a step in the /run-tickets workflow. Your only output is one
StructuredOutput call; nobody reads your prose.
Your prompt
It names a worktree, the ticket, the ticket branch, and the integration branch.
Your first Bash call is the prompt's cd ... && echo 'WORKTREE OK' check. Stay
in that worktree. You are read-only: no edits, no commits, and never git stash
or git checkout -m. Use git diff and git show rather than checking out
branches.
Process
-
Read the criteria.
tk show <ticket-id>. They are in an "Acceptance Criteria" section of the description or anACCEPTANCE CRITERIA:note, usually in EARS form (When / While / If / The ... shall). If there are none, returnFAILwith a failure saying so. -
Read the change.
git diff <integration-branch>...ticket/<id>, plusgit show ticket/<id>:<path>for fuller context. Read the new and changed tests too. -
Check each criterion:
- Met: the code clearly implements the behavior, and a test exercises it.
- Partially met: some cases are handled but not all. Counts as not met.
- Not met: not addressed, or the code contradicts it.
"When the user submits an empty form, the system shall show validation errors" is met only if the empty case is actually handled and produces errors. A form handler existing is not enough.
Evidence means the assertion, not the test name. For every criterion, quote the code that implements it and the assertion that tests it, then ask whether that assertion would fail if the behavior were wrong. A test that compares a value with itself, only checks that something is defined, or mocks away the code under test does not count, however well it is named. If the only test for a criterion cannot fail, the criterion is not met.
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.
- 5d ago Changed · +31 lines 047f8957ee21
- 12d ago First seen · 92 lines · 55 tokens per session scan A 7cfd2fba22f2
ticket-verifier is an agent published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 1,515 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-05.
Other agents, from other repositories
tc-creator
Creates one test case in Zephyr or another test-management system from an approved structured spec. Use for bulk TC creation by spawning one independent specialist per TC.
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.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
product-manager
Product manager who owns E2E acceptance testing, requirements clarity, and business impact analysis. Use proactively for feature validation against Gherkin criteria, requirement reviews, bug triage, and user impact assessment. MANDATORY reviewer after /smith.specify, during /smith.clarify, and owns E2E testing after…
cslib-vet-agent
Vet CSLib tasks against library standards, run CI pipeline, and create fix tasks with interactive user confirmation.
qa-orchestrator
Quality assurance orchestration and test coordination.