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/tandnguyendev/dev-workflow/statusgit clone --depth 1 https://github.com/tandnguyendev/dev-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.00026 | $0.00308 |
| Opus 5 | $0.00013 | $0.00154 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
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
Report the current state of the dev-workflow feature in progress. Do this by reading the project's working docs (do NOT rely on conversation memory):
- Resolve the active feature: read
.dev-workflow/activefor the slug, then readspec.md,plan.md,phase-log.mdfrom.dev-workflow/features/<slug>/. Fall back to the project root for the legacy single-feature layout. Read.approval-gateat the repo root if present. - Print a concise status:
- Active feature (from the spec/phase-log title).
- The chosen solution in one line (from
spec.md), if decided. - Phases: how many are USER APPROVED vs total, and which phase is current /
next (the first not-yet-approved phase in
phase-log.md). - Any outstanding review findings recorded for the current phase.
- Approval gate state (LOCKED / UNLOCKED / not set).
- The single most useful next action.
- If none of these files exist, say there is no active dev-workflow feature and
suggest running
/dev-workflow:initand/dev-workflow:feature.
Keep it short — this is a status readout, not a full report. Do not modify any files.
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 · 25 lines · 26 tokens per session scan A 77d4ce35b7d2
status is a command published in the GitHub repository tandnguyendev/dev-workflow (2 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 308 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.