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.
git clone --depth 1 https://github.com/alexsds/ade-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/commands/alexsds/ade-workflow/done)<a href="https://agentmods.dev/commands/alexsds/ade-workflow/done"><img src="https://agentmods.dev/badge/commands/alexsds/ade-workflow/done/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/commands/alexsds/ade-workflow/done"><img src="https://agentmods.dev/badge/commands/alexsds/ade-workflow/done.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.00231 |
| Opus 5.5 | $0.00002 | $0.00092 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 6mo ago), licensed MIT. It adds 6 tokens to every session and 231 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
ccc-rules-distill
Scan installed skills for principles that recur across them and propose them as rules, writing only what you approve. Use when skills repeat the same guidance or the rules directory has drifted from them.
design
A command that turns an existing plan into a detailed technical design for building the feature.