Borrowing it
Nothing to install: this file belongs to pyramidheadshark/claude-scaffold. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pyramidheadshark/claude-scaffold/main/.claude/commands/dev-status.mdgit clone --depth 1 https://github.com/pyramidheadshark/claude-scaffoldWrote 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/pyramidheadshark/claude-scaffold/dev-status)<a href="https://agentmods.dev/commands/pyramidheadshark/claude-scaffold/dev-status"><img src="https://agentmods.dev/badge/commands/pyramidheadshark/claude-scaffold/dev-status/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/pyramidheadshark/claude-scaffold/dev-status"><img src="https://agentmods.dev/badge/commands/pyramidheadshark/claude-scaffold/dev-status.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.00000 | $0.00275 |
| Opus 5.5 | $0.00000 | $0.00110 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
dev-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 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
/dev-status
Updates dev/status.md to reflect the current state of the project.
Run this command:
- Before ending any work session
- After completing a significant task
- When switching focus to a different part of the project
What to Update
- Check off completed backlog items
- Move the active phase marker if a phase was completed
- Add any new issues discovered and their solutions
- Log any architectural decisions made
- Update "Next Session Plan" with the 2-3 most important next actions
- Update "Files to Know" if new critical files were added
Instructions for Claude Code
Read the current dev/status.md, then update it by:
- Comparing the completed tasks list against what was actually done this session
- Adding new items to "Known Issues and Solutions" if any blockers were hit
- Recording any new architecture decisions in the decisions table
- Writing a concrete "Next Session Plan" — not vague, but specific actionable steps
- Updating the "Last updated" timestamp
Keep the file concise. If "Completed" items list grows beyond 15 items, archive the oldest ones to dev/archive/status-{date}.md.
Never summarize away the "Known Issues and Solutions" section — this is the most valuable part for future sessions.
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 · 32 lines · 0 tokens per session scan A e8fbcfe45178
dev-status is a command published in the GitHub repository pyramidheadshark/claude-scaffold (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 275 tokens. 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
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
team
Virtual eng team orchestrator. Runs a goal end-to-end through the whole team — strategy → plan → build → QA → ship — conducted by the engineering-manager, delegating to every specialist. One entry point that connects /ceo-review, /eng-review, /qa, and /ship.
content-start
Content production session start command. Gives the daily content session a structured start, shows pending work, and sets priorities.
proposal
Client proposal command. Builds a professional client proposal from project summaries. Valid for 30 days.
dashboard
Daily statistics panel. Presents task, audit, event, and performance data as a unified table.