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/dean0x/devflowWrote 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/dean0x/devflow/implement-revalidate)<a href="https://agentmods.dev/commands/dean0x/devflow/implement-revalidate"><img src="https://agentmods.dev/badge/commands/dean0x/devflow/implement-revalidate/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/dean0x/devflow/implement-revalidate"><img src="https://agentmods.dev/badge/commands/dean0x/devflow/implement-revalidate.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.00000 | $0.00313 |
| Opus 5.5 | $0.00000 | $0.00125 |
| Sonnet 5.5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
implement-revalidate 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 yesterday.
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
Implement: re-validation
Read by /implement when the user asks to re-validate (D-CMD-REF-HAND).
Continuation path
When the user explicitly asks to re-validate, re-check, or re-run quality gates after making their own changes:
- Branch safety check: If on a protected branch (main, master, develop, etc.), run Phase 1 to create/switch to a work branch. If already on a work branch, skip Phase 1.
- Skip Phase 2 — no Code agent needed, user already made changes.
- Record BASE_BRANCH: unless Phase 1 ran, take the PR's base (
gh pr view --json baseRefName --jq .baseRefName), else the remote default branch. Stop the run unless it matches^[A-Za-z0-9._/+@,#-]{1,200}$, telling the user it allows only ASCII letters, digits and._/+@,#-, at most 200. Phases 3-7 run{branch_diff}from it. - Run Phases 3-8 — Polish, Self-Review, Alignment, the one full Validate, QA Testing and the conditional Re-Validate, on the branch diff.
- Proceed to Phase 9 (Open PR), Phase 11 (Evidence) and Phase 12 (Report).
If the user prompt does NOT match re-validation, proceed with the full pipeline below.
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.
- yesterday Changed d67fe86e0d92
- 2d ago First seen · 16 lines · 0 tokens per session scan A 7c510c4fe3e1
implement-revalidate is a command published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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-14.
Other commands, from other repositories
build
Implement the next task incrementally — build, test, verify, commit.
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.