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/daphnee-ovo/dev-flowWrote 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/commands/daphnee-ovo/dev-flow/test)<a href="https://agentmods.dev/commands/daphnee-ovo/dev-flow/test"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/test/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/commands/daphnee-ovo/dev-flow/test"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/test.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.00016 | $0.00480 |
| Opus 5.5 | $0.00006 | $0.00192 |
| Sonnet 5.5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
test 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
TEST — Test execution
/test is the explicit TEST-phase workflow entry. Do not invoke it from Task
completion or a hook reminder; ask the user to enter TEST instead. The dow test
CLI is the only test executor and the only component that creates test-failure
ISSUE files.
Commands
Full project test:
dow test
Task-scoped test:
dow test TASK-ID
dow test TASK-ID reads the matching Task from both active task_* and
completed done_task_* files, then runs its files.test. An empty test list is
PASS. Paths are relative to project_root.
Configuration
Create .dev-doc/test.ci when project defaults do not fit:
devtest:
run: <Task test command>
test:
run: <full project test command>
The command runs in project_root with inherited environment variables.
Available placeholders are project_root, task_id,
task_file, and test_files. Unknown placeholders and missing tools
are PRECONDITION_FAILED.
Without custom commands, the CLI uses built-in adapters for Rust, Go, Python pytest, JavaScript/TypeScript package test scripts and runners, and compatible Shell tests. Unsupported files or runners are precondition failures; they are not silently executed as Shell.
Outcomes
PASSexits 0.TEST_FAILEDexits 1, returns the original test output, and creates a P1 ISSUE withsource: test.PRECONDITION_FAILEDexits 2, returns the prerequisite error, and does not create an ISSUE.
The ISSUE title is Test fail:<summary> for full tests and
Test TASK-ID fail:<summary> for Task tests. Generated ISSUE Markdown may
contain files_modify and files_create; public issue create/update input
uses the nested files object.
There is no --file or --task test selector. Use the language's own command
for an ad hoc single-file check, or configure test.ci.
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 · 67 lines · 16 tokens per session scan A bfe49d82eb46
test is a command published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 480 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 commands, from other repositories
test
A command that recommends the smallest useful set of checks for a project's type and explains what each check does.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
write-skill-test
RED-GREEN-REFACTOR implementation for writing-skills: Baseline testing, minimal skill writing, loophole closure, and full creation checklist.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.
tester
You are an exacting senior software tester — a quality gatekeeper who assumes code fails until proven otherwise. You find the failure cases others miss, never accept vague assurances, and never let gaps in test coverage slide.