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/parkerm2/create-claude-workflow/statusgit clone --depth 1 https://github.com/ParkerM2/create-claude-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.00019 | $0.01071 |
| Opus 5 | $0.00010 | $0.00535 |
| Sonnet 5 | $0.00004 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/status — Show Feature Implementation Progress
Invoke this skill to see a formatted summary of the active feature's progress. Quick at-a-glance view without reading the full progress file.
When to Use
- You want a quick overview of where a feature stands
- You need to check how many tasks are complete vs remaining
- You want to see QA results and blocker status
- You're returning to a session and want to orient yourself
Phase 1: Find Active Feature
Scan for the active feature progress file:
# List progress files
ls the progress directory/
If multiple progress files exist, identify the active one:
- Look for files with Status other than COMPLETE
- If multiple are in-progress, present the most recently updated one
If no progress files exist:
No active features found in .claude/progress/.
To start a new feature: /new-plan "description" then /agent-team
Stop here.
Phase 2: Parse Progress File
Read the feature's tracking data. First check for current.md (pre-rendered summary):
# Quick path — read pre-rendered summary
cat the progress directory/<feature>/current.md
If current.md exists and is recent (< 5 minutes old), display it directly.
If stale or missing, regenerate from events.jsonl:
- Read
the progress directory/<feature>/events.jsonl - Extract: feature name, status, tasks, blockers, last checkpoint, timestamps
- Render the summary below
Data to extract from events:
- Feature name — from event
featurefield - Status — COMPLETE if
session.endexists, else IN_PROGRESS - Task list with statuses — from
task.started/task.completed/task.failedevents - QA results — from
qa.passed/qa.failedevents - Branch status — from
branch.created/branch.mergedevents - Blockers — from
blocker.reportedevents (check if resolved) - Timestamps — first and last event timestamps
Phase 3: Display Summary
Format and display the summary:
FEATURE STATUS:
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.
- 2d ago First seen · 165 lines · 19 tokens per session scan A 575f64be42cf
status is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,071 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.