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/statusgit 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.00008 | $0.00193 |
| Opus 5 | $0.00004 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
status 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 reporting ADE workflow status.
Step 1: Find active plan
Look in .ade/docs/plans/ for any plan files. If none exist, tell the user no active plan exists.
Step 2: Read plan details
Read the plan file. Report:
- Project name and date
- Plan status (draft/approved/in-progress/completed/archived)
- Ticket number (if jira style)
Step 3: Report feature progress
List each feature/phase from the plan. For each, check git log for related commits to determine what has been implemented.
Step 4: Report recent evaluator scores
If the build is in progress, check for any evaluator feedback in recent conversation or committed files. Report last known scores.
Step 5: Identify blockers
Note any features that appear incomplete or where the evaluator reported failures that haven't been addressed.
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 · 29 lines · 8 tokens per session scan A fce26f78edba
status is a command published in the GitHub repository alexsds/ade-workflow (1 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 193 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.