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/biggora/claude-plugins-registry/define-donenpx skills add biggora/claude-plugins-registry --skill define-donegit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/define-done)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/define-done"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/define-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.1 | $0.00077 | $0.00740 |
| Opus 5 | $0.00039 | $0.00370 |
| Sonnet 5 | $0.00015 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
define-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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Define Done
Convert the request into an agreed outcome before implementation. Make every completion claim traceable to executable evidence.
Workflow
-
Inspect the repository before asking questions.
- Read applicable repository instructions, architecture, tests, issue context, and existing planning conventions.
- Distinguish discoverable facts from product decisions. Resolve facts from the repository instead of asking the user.
- Preserve existing work. Read
AGENTS.mdandCLAUDE.mdwhen present, but never overwrite either file automatically.
-
Resolve material ambiguity.
- State the current interpretation and any assumption that could change scope or behavior.
- Ask one material question at a time. Prefer a small set of meaningful choices with a recommendation when trade-offs exist.
- Stop rather than silently choose when the answer would materially change the outcome.
-
Define the product outcome.
- Name the user and their job-to-be-done.
- State one product goal in observable terms.
- Describe the happy path and the scenarios required for release.
- Separate in-scope behavior from explicit non-goals.
- Record applicable technology, compatibility, performance, and security constraints.
- Define
ALWAYS,ASK, andNEVERboundaries for actions and side effects.
-
Write 3–7 executable acceptance criteria.
- Express each criterion as
Given/When/Thenbehavior, not an implementation preference. - Attach a project-owned command, test, inspection, or artifact that can prove the result.
- Include expected observable evidence and relevant failure behavior.
- Do not weaken a criterion merely to match the current implementation.
- Express each criterion as
-
Record the specification.
- Follow an existing repository convention when one exists.
- Otherwise write
.agent/specs/<slug>.mdusing the specification template. - Use the bug/no-change variant in that reference when correctness of the existing code is uncertain.
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 · 61 lines · 77 tokens per session scan A 368be9f5ef47
define-done is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 740 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…