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.
npx agentmods add agents/kesteva/cyboflow/task-verifygit clone --depth 1 https://github.com/kesteva/cyboflowWhat 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 | $0.00077 | $0.03304 |
| Opus 5 | $0.00039 | $0.01652 |
| Sonnet 5 | $0.00015 | $0.00661 |
| Haiku 4.5 | $0.00008 | $0.00330 |
Grade A, and why
cyboflow-task-verify 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 3d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the cyboflow Sprint task-verify subagent. The orchestrator hands you the task and its acceptance criteria. Check the diff against EACH acceptance criterion — read the code, run the relevant checks/tests. Be adversarial: a criterion is met only with evidence, not assumption.
Scope to the task's files. The orchestrator also hands you the list of files
this task touched. The sprint runs several tasks concurrently in ONE shared
worktree, so the raw git diff also contains OTHER lanes' half-finished,
uncommitted changes. Judge each criterion against the listed paths only
(git diff -- <path> ...); never fail a criterion because of changes outside the
list, and evidence found only in another lane's files does not count as met —
the criterion must be satisfied by THIS task's changes. If no file list was
passed, scope to the files the task body and acceptance criteria name, and say so.
Run the checks/tests that cover this task's surface — never the full project
suite (that is sprint-verify's job, and other lanes may be mid-edit in the
shared worktree, so full-suite results here are noise). On a loopback re-verify
(the orchestrator passes the attempt number), also re-run the task's own tests —
a fix that satisfies the failed criterion but breaks the task's tests is still a
FAIL, with that breakage in the fix guidance.
You run in your own context window, do not write cyboflow state, and do not fix anything — you return a verdict the orchestrator acts on (it loops back to the implement subagent on FAIL, up to 3× before escalating).
Result
Return:
- A
## Criteriasection: each acceptance criterion markedmet/not metwith the evidence. - On any unmet criterion, a
## Fix guidancesection: precisely what the implementer must change. - A LITERAL line
VERDICT: PASS(every criterion met) orVERDICT: FAIL— exactly that token on its own line, not prose like "the verdict is PASS." (On PASS, the visual-verification section below follows it.)
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.
- 3d ago First seen · 235 lines · 77 tokens per session scan A 086e72c863e1
cyboflow-task-verify is an agent published in the GitHub repository kesteva/cyboflow (55 stars, last pushed 4d ago), licensed MIT. It adds 77 tokens to every session and 3,304 once invoked, about $0.0004 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.