Borrowing it
Nothing to install: this file belongs to TimothyVang/verdict-dfir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TimothyVang/verdict-dfir/master/.claude/skills/dev-loop/SKILL.mdgit clone --depth 1 https://github.com/TimothyVang/verdict-dfirWrote 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/skills/timothyvang/verdict-dfir/dev-loop)<a href="https://agentmods.dev/skills/timothyvang/verdict-dfir/dev-loop"><img src="https://agentmods.dev/badge/skills/timothyvang/verdict-dfir/dev-loop/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/skills/timothyvang/verdict-dfir/dev-loop"><img src="https://agentmods.dev/badge/skills/timothyvang/verdict-dfir/dev-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00204 | $0.03573 |
| Opus 5.5 | $0.00082 | $0.01429 |
| Sonnet 5.5 | $0.00041 | $0.00715 |
| Haiku 4.5 | $0.00020 | $0.00357 |
Grade A, and why
dev-loop 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Loop
Take one coding task from "asked" to "verifiably done, clean, committed, and proposed as a PR" through a short feedback loop you can defend. The point is not autonomy — it is a loop with a real acceptance gate, a quality bar, and named stopping conditions, so the work ends in a green build or an honest "blocked", never in a confident claim that isn't true.
Treat this like the project's own evidence ethic: no claim of done without a receipt you can re-run. A passing test you executed is a receipt. "It should pass" is not.
The contract (read once, then hold it the whole loop)
- Isolate the work in a git worktree so the main checkout is never disturbed and the diff stays clean (next section).
- Keep a resumable plan on disk and check it off as you go, so an interrupted run picks up where it left off instead of starting over.
- Define done before you act. Write the Definition of Done as an observable, reproducible checklist first. If you cannot state the command whose exit code decides "done", you are not ready to act — go back and make the goal checkable.
- Clear the quality bar, not just the test. Done means clean code and sound logic too —
see
references/quality-bar.md. A green test over sloppy code is not done. - One bounded change per cycle. Smallest reversible step toward the DoD, then verify.
- Re-read fresh state before consequential actions. Don't ship against stale code.
- Preserve unrelated work. Keep the diff surgical. Never "clean up" code the task didn't ask about.
- Never report an error, a skipped step, or an exhausted budget as success. A red test is red. Say so, with the output.
- Stop on a named terminal state, not on vibes (see Terminal states).
Work in an isolated worktree
Run the whole loop in a dedicated git worktree, not the main checkout. This keeps unrelated uncommitted work safe, keeps your diff clean, and lets a run be abandoned without leaving a mess. Create it from the branch you'll ship:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 234 lines · 204 tokens per session scan A 929408d8c221
dev-loop is a skill published in the GitHub repository TimothyVang/verdict-dfir (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 204 tokens to every session and 3,573 once invoked, about $0.0008 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-09-04.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
gh-issue
Fetch GitHub issue, create branch, plan and implement with TDD, then open PR.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
loom-builder-pr
This document covers PR creation, test output handling, and quality requirements for the Builder role. For the core builder workflow, see builder.md.