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/shrekshrek/project-workflow/feature-donenpx skills add shrekshrek/project-workflow --skill feature-donegit clone --depth 1 https://github.com/shrekshrek/project-workflowWrote 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/shrekshrek/project-workflow/feature-done)<a href="https://agentmods.dev/skills/shrekshrek/project-workflow/feature-done"><img src="https://agentmods.dev/badge/skills/shrekshrek/project-workflow/feature-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.00028 | $0.00341 |
| Opus 5 | $0.00014 | $0.00170 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
feature-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 4d 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
Feature Done
Match the user's language. Read ${CLAUDE_PLUGIN_ROOT}/docs/actions/feature-done.md completely before acting. Fresh reviewer agents read their canonical specs; the main session reads one only when executing the allowed fallback.
Claude execution details:
- Resolve
$ARGUMENTSthrough the shared active-feature rules; excludearchive/. Review applicability follows the actual risk and project requirements, not file names. - Execute the complete canonical action with Bash against its selected Git population. A stop still writes the canonical receipt.
- Resolve the canonical convention population and dispatch
spec-reviewerandagents-md-revieweras directed. Claude L2 may include project-root.claude/rules/; include user-level~/.claude/rules/only when selected. - Capture the reviewed Git identity before endpoint-owned writes, then persist and structurally re-read the canonical
## Proof Bundlereceipt. For a non-READY verdict, map each blocker or blocker group to the canonicalNextroute before returning control under the action's continuation rules. Return the action's concise human summary withLifecycle: READY; archive pendingwhen applicable and a repository-relative link to the resolved receipt (defaultspec.md#proof-bundle); the full receipt remains on disk.
Apply the canonical verdict contract. Finish/delivery stops at READY with archive pending; enclosing
close/archive/submit intent continues to /project-workflow:feature-archive for the explicit feature.
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.
- 4d ago First seen · 21 lines · 28 tokens per session scan A fdc7cee3087e
feature-done is a skill published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 341 once invoked, about $0.0001 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
iso-24495-2
Sector-specific Plain Language standard for legal communication (ISO 24495-2:2025). Applied during contract drafting, license review, and legal/compliance writing.
configuration-management
Secrets management, environment-specific configs, safe defaults, feature flags, configuration-as-code, compliance and audit trails. Use when managing secrets, configuring deployments, or implementing feature flags.
dependency-management
Version updates (major/minor/patch), security patch application, transitive dependency resolution, monorepo dependency management, deprecation tracking, license compliance. Use when updating dependencies, managing versions, or addressing CVEs.
motherduck-security-governance
Explain MotherDuck security, governance, and access-control patterns. Use for any question about SOC 2, GDPR, compliance, data residency, regions, SSO, service accounts, token handling, tenant isolation, sharing boundaries, snapshots and recovery, or governance posture — including when a securitycomplianceowner…
Amend
Formally amend the constitution, with mandatory impact analysis before any change lands. The constitution is supreme law; amendments are versioned and their downstream effects scanned first.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…