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 skills/codoop/codoop-flow/definition-of-donenpx skills add Codoop/codoop-flow --skill definition-of-donegit clone --depth 1 https://github.com/Codoop/codoop-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/skills/codoop/codoop-flow/definition-of-done)<a href="https://agentmods.dev/skills/codoop/codoop-flow/definition-of-done"><img src="https://agentmods.dev/badge/skills/codoop/codoop-flow/definition-of-done.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00975 |
| Opus 5 | $0.00018 | $0.00487 |
| Sonnet 5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
definition-of-done 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Definition of Done
Conversation Profile
When codoop_flow.toml is available, read user_role; a missing value means
general. It applies only to this conversation: use normal professional terms
inside the user's field, and explain cross-field topics in plain language. The
user may override it for the current conversation by asking for simpler or more
professional language. Never apply the profile to code, PRD, Spec, Plan, Todo,
reports, agent prompts, or other generated files; those stay precise and
professional.
Project-level standards that every completed task must satisfy. Unlike acceptance criteria (which vary per task), DoD is a fixed quality baseline.
Definition of Done vs. Acceptance Criteria
| Acceptance Criteria | Definition of Done | |
|---|---|---|
| Scope | Specific to one task or spec | Applies to every increment |
| Changes | Different per task | Fixed and unchanging |
| Answers | "Did we build this correctly?" | "Can we confidently ship this?" |
| Defined By | During task planning | Project-level standard |
| Example | "User can reset password" | "Tests pass, no regressions, docs updated" |
Key: A task is only done when it meets both its acceptance criteria and the Definition of Done.
Completion Standards Checklist
Before declaring a task complete, ensure all items below are satisfied:
Correctness
- All acceptance criteria are met
- Code runs and behaves as intended (verified at runtime, not just compiled or typechecked)
- New functionality is covered by tests: tests fail without the change, pass with it
- Existing tests still pass (no regressions)
- Edge cases and error paths are handled, not just the happy path
Quality
- Code clearly expresses intent through naming and structure; no comments needed to understand what it does
- No duplicated business logic
- No dead code, debug output, or commented-out blocks
- Changes are scoped to the task; no unrelated refactors snuck in
- Code passes linting and formatting checks
What ships with it
1 file 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.
- 5d ago First seen · 111 lines · 37 tokens per session scan A 9c04d14e810f
definition-of-done is a skill published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 11d ago), licensed MIT. It adds 37 tokens to every session and 975 once invoked, about $0.0002 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-31.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
agent-safety
Use when bounding an LLM agent that already runs — scoping its task domain, gating tools to least privilege, defending against prompt injection in untrusted web/email/RAG text, requiring human approval on irreversible actions, capping runtime and cost, or triaging what it already did. NOT building the loop, tools, or…
chatbot
Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is building-agents), NOT a human answering one ticket…
aegisops-ai-v2
/aegisops-ai — Autonomous Governance Orchestrator workflow skill. Use this skill when the user needs Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance and the operator should preserve the upstream workflow, copied support…
antidote
Stop AI agents from patching symptoms. Use this skill when coding, reviewing, refactoring, auditing, committing fixes, or adding guards, validation, workarounds, or 20+ lines without deleting code.
anti-slop-design
Category-aware design skill that builds distinctive, production-grade UIs. Brand-vs-product register, color strategy commitment, scene-based theme choice, palettes, font pairings, UX patterns, shadcn/token integration, empty-error-loading copy, secondary slop signals, multimodal design parity from mocks, and a…