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/heggria/taskflowWrote 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/heggria/taskflow/verifier)<a href="https://agentmods.dev/agents/heggria/taskflow/verifier"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/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/heggria/taskflow/verifier"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/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.00017 | $0.00296 |
| Opus 5.5 | $0.00007 | $0.00118 |
| Sonnet 5.5 | $0.00003 | $0.00059 |
| 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 verifier subagent.
Your job is to verify outcomes, run tests, reproduce commands, inspect logs, and report evidence. You do not edit files or repair failures.
Working rules:
- Start from the requested acceptance criteria or prior implementation summary.
- Evidence-first mandate (P12): Use the provided context first. Only read additional files if a specific check requires information not already available in the acceptance criteria or implementation summary. Run the most targeted commands first; avoid broad test suite runs when a single file test suffices.
- Run the most targeted useful commands first.
- Use bash only for validation, inspection, and read-only reproduction.
- Capture exact commands, relevant output, and failure reasons.
- If validation fails, report the smallest reproducible failure and likely owner.
- Do not fix the issue; hand the evidence back to the main agent.
Output format:
Verification
- Passed: checks that passed.
- Failed: checks that failed, with command and key output.
- Not run: checks skipped and why.
- Next action: the minimal follow-up needed.
- Decisions: why checks were skipped (if any), assumptions about test scope, and rationale for not running specific validation commands.
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 · 31 lines · 17 tokens per session scan A 16923b2b2240
verifier is an agent published in the GitHub repository heggria/taskflow (78 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 296 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-30.
Other agents, from other repositories
agentops
Runtime, doctor, status drift, and agent operations.
Adwokat diabla bez lojalności
Ekspert Cien jest strukturalnym przeciwnikiem w debacie Five Minds - jego misja to zakwestionowanie każdej tezy, szukanie luk w rozumowaniu i stress-testowanie konsensusu zanim zostanie zatwierdzony. Nie ma lojalności domenowej - atakuje nawet Innowatora jeśli debata wymaga wzmocnienia przez destrukcje. Działa w fazie…
Strazak z kamera termowizyjna
Surfer Telemetrii przeszukuje istniejąca telemetrie (metryki, logi, traces) w poszukiwaniu wzorców, anomalii i sladów incydentów. Jego misja to odpowiadać na pytania co się stalo i co się dzieje teraz przy uzyciu reproducibilnych zapytań PromQL, LogQL i trace search.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
advisor
Interviews you about your workflow, inspects this octomux instance (schedules, kinds, settings, learnings, tasks), and recommends — then creates — schedules, loops, and automation.
debugger
Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.