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 adamfaik/claude-code-pm-starter --skill status-updategit clone --depth 1 https://github.com/adamfaik/claude-code-pm-starterWrote 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/adamfaik/claude-code-pm-starter/status-update)<a href="https://agentmods.dev/skills/adamfaik/claude-code-pm-starter/status-update"><img src="https://agentmods.dev/badge/skills/adamfaik/claude-code-pm-starter/status-update/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/adamfaik/claude-code-pm-starter/status-update"><img src="https://agentmods.dev/badge/skills/adamfaik/claude-code-pm-starter/status-update.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.00038 | $0.00367 |
| Opus 5.5 | $0.00015 | $0.00147 |
| Sonnet 5.5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
status-update 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
Status update
Draft the update the user owes someone, from files, not from their memory.
Steps
- Find the state. Read the active project's
tasks.md(Status notes first, then Now / Next / Blocked) and anyoperations/notes dated since the last update. If several projects are active, ask which ones the update covers. - Ask two things only: who the update is for, and where it will be posted (email, Slack, a doc). Skip the questions if the conversation already says.
- Draft it in the user's voice per
context/preferences.md. Default shape, unless preferences say otherwise:- One line on the headline: the single most important thing that moved or didn't.
- What shipped or progressed, with the concrete result.
- What's blocked, with the specific ask that would unblock it. An update without an ask is a diary entry.
- What's next.
- Match the channel. Slack gets short lines and no headings; email gets a subject line; a doc gets the full shape.
Rules
- Every claim of progress points at something real: a merged change, a decision made, a number moved, a meeting outcome. No "good progress on X".
- Blockers name the blocker, not just the feeling. "Waiting on legal's read of the data clause since the 12th" beats "legal is slow".
- After the user approves the draft, update
tasks.md's Status notes so the next update starts from today's truth.
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 · 26 lines · 38 tokens per session scan A a8c8a0231f00
status-update is a skill published in the GitHub repository adamfaik/claude-code-pm-starter (13 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 367 once invoked, about $0.0002 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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.