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 commands/alexsds/ade-workflow/donegit clone --depth 1 https://github.com/alexsds/ade-workflowWhat 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.00006 | $0.00231 |
| Opus 5 | $0.00003 | $0.00115 |
| Sonnet 5 | $0.00001 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
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 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
You are executing the ADE archive workflow.
Step 1: Find the current plan
Look in .ade/docs/plans/ for the current plan. Read it.
Step 2: Verify completion
Check that the plan status is in-progress or completed. If it's still draft, warn the user that the plan hasn't been built yet.
Step 3: Add completion metadata
Append the following to the end of the plan file:
---
## Completion Summary
- **Date completed:** [today's date]
- **Git commit range:** [first commit..last commit for this plan]
- **Features implemented:** [count from the plan]
Step 4: Update status and archive
Update the plan frontmatter status to archived.
Move the plan file from .ade/docs/plans/ to .ade/docs/archive/.
Step 5: Confirm
Tell the user: "Plan archived to .ade/docs/archive/. Ready for the next project — use /ade:plan to start a new one."
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 First seen · 38 lines · 6 tokens per session scan A 3f8c83de573d
done is a command published in the GitHub repository alexsds/ade-workflow (1 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 231 once invoked, about $0.0000 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 commands, from other repositories
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
test
Design or run focused test validation for a task, bug, or diff.
mvp-spec
Research and produce a strict MVP spec with small 1-2 hour tasks and explicit out of scope.
research
Research a technical or product question.
goal
Set a goal and enter the RALPH loop — keep working autonomously until the goal is genuinely done or the user stops you. Use /goal "objective" to start, /goal status to check, /goal complete to finish, /goal clear to stop.
review-pr
Command "review-pr" from saski/arnesto, covering review pr, what this command does, workflow steps, phase 0: initialize review and phase 1: analysis & summary.