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/16wells/claude-project-setupWrote 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/16wells/claude-project-setup/project-status)<a href="https://agentmods.dev/commands/16wells/claude-project-setup/project-status"><img src="https://agentmods.dev/badge/commands/16wells/claude-project-setup/project-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/16wells/claude-project-setup/project-status"><img src="https://agentmods.dev/badge/commands/16wells/claude-project-setup/project-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.00010 | $0.00198 |
| Opus 5.5 | $0.00004 | $0.00079 |
| Sonnet 5.5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
project-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
Give the user a concise status read on this client project. You must:
- Read
CLAUDE.mdto ground yourself in the project. - Read
01-context/decisions-log.mdand report:- Number of closed decisions
- Any open decisions and why they're open
- Any outstanding items the client owes us
- Read the last 5 entries of
01-context/activity-log.mdand report what's been worked on recently. - Read
01-context/insights.mdand surface any recent observations that seem relevant. - Scan
02-deliverables/and list what's been produced. - Call out anything that looks stale or blocked.
Keep the summary tight — one screen. The user should be able to read it in 60 seconds and know exactly where things stand. If something needs a decision from them, say so explicitly.
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 · 18 lines · 10 tokens per session scan A 7822348a825e
project-status is a command published in the GitHub repository 16wells/claude-project-setup (2 stars, last pushed 13d ago), licensed MIT. It adds 10 tokens to every session and 198 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
session-end
Thin wrapper (GETSITREP-10) over getsitrep session-end — the CLI owns the Session Log entry, header updates, .sitrep-data.json, the history record, and the commit. This file's only remaining job is the one step no CLI can do on its own: building the session-summary JSON from this conversation, since a CLI has no way…
capture
Capture a new task into the project plan and status report in one step. Never lose an idea mid-session.
sitrep
Thin wrapper (GETSITREP-10) — reading STATUSREPORT.md, the session-command tracker (absorbed from the old /pulse, see docs/specs/command-canon.md), and the next-command suggestion logic all live in getsitrep sitrep.
sync-todos-to-github
Convert TodoWrite task list to GitHub plan issue (triggers automation).
dewey-classify
Classify a file using the DeweyGraph modular skill toolkit.
dewey-graph
Show the DeweyGraph link graph and heat maps for the current archive.