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 skills add nasrulhazim/claude --skill project-statusgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/skills/nasrulhazim/claude/project-status)<a href="https://agentmods.dev/skills/nasrulhazim/claude/project-status"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/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/skills/nasrulhazim/claude/project-status"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/project-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 26 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00190 | $0.01597 |
| Opus 5 | $0.00095 | $0.00798 |
| Sonnet 5 | $0.00038 | $0.00319 |
| Haiku 4.5 | $0.00019 | $0.00160 |
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 5d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project status
Report in the house style: TLDR first, then tables, minimal prose. No narrative paragraphs, no per-document walkthrough. A status report is a decision aid, not a diary.
The one rule
Never report a document's claim as status without checking the code.
Planning documents go stale within days of being written. A file saying "not built" is a claim to verify, not a fact — and the failure is asymmetric: reporting built work as outstanding sends someone to rebuild it, while the reverse merely delays a discovery. The same applies to open issues. An issue that is open and already built is the single most common defect in these reports.
Where the truth lives
| Source | Good for | What it lies about |
|---|---|---|
documentation/03-planning/tasks/*.md |
One file per feature; most carry a **Status:** line and a per-phase table |
Goes stale within days — every claim needs a code check |
documentation/03-planning/*triage*.md / *-mvp-scope.md |
The ordered "order of attack" and a running open/closed count | Snapshot-dated. Check its date against today before quoting any count |
gh issue list |
The only live count | An open issue is often already built |
gh api .../milestones |
Burn-down per phase | A milestone with no issues is not the same as a finished one |
CLAUDE.md gotchas |
Corrections worth not repeating | Not status |
| The code | Final authority | — |
If the project keeps a lessons.md in its planning tree, read it for context — but new
corrections belong in CLAUDE.md, where every session picks them up.
Gather
These are cheap and cover almost everything. Run them before reading a single plan.
# Live issue counts
gh issue list --state open --limit 200 --json number,title,labels \
--template '{{range .}}#{{.number}} {{.title}} {{range .labels}}{{.name}},{{end}}
{{end}}'
# Milestone burn-down
gh api repos/:owner/:repo/milestones \
--jq '.[] | "\(.title)\topen=\(.open_issues)\tclosed=\(.closed_issues)"'
# What shipped recently — anchors the TLDR
gh issue list --state closed --limit 30 --json number,title,closedAt \
--template '{{range .}}#{{.number}} {{.closedAt}} {{.title}}
{{end}}'
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +6 lines 1c2813f56d67
- 9d ago First seen · 129 lines · 190 tokens per session scan A 9fa7ed545dde
project-status is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 7d ago), licensed MIT. It adds 190 tokens to every session and 1,597 once invoked, about $0.0010 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.