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 aakashg/pm-claude-skills --skill status-update-writergit clone --depth 1 https://github.com/aakashg/pm-claude-skillsWrote 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/aakashg/pm-claude-skills/status-update-writer)<a href="https://agentmods.dev/skills/aakashg/pm-claude-skills/status-update-writer"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-skills/status-update-writer/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/aakashg/pm-claude-skills/status-update-writer"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-skills/status-update-writer.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 56 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.00055 | $0.02409 |
| Opus 5 | $0.00028 | $0.01205 |
| Sonnet 5 | $0.00011 | $0.00482 |
| Haiku 4.5 | $0.00006 | $0.00241 |
Grade A, and why
status-update-writer 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 12d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Update Writer
Turn messy notes into a precise stakeholder update that stands alone without a follow-up meeting.
Step 0 — Read first
| Source | Path | What to extract |
|---|---|---|
| User's raw notes | whatever they pasted | What actually shipped, real numbers, real dates, real names |
| Project context | CLAUDE.md |
North star metrics, OKRs, company terminology, audience norms |
| Cadence formats | references/cadences.md |
Daily / monthly / QBR variants of the base format |
| Last update | any prior update they name | What was promised last week — the delta is the story |
| Metrics source | dashboard link or data they provide | Current values only. Never estimate a metric. |
If the user gave you no numbers, the update stays qualitative and you say so. Do not fill the gap.
Constraints
Mandatory.
- Total update under 200 words for the weekly default.
- Never fabricate progress. If the notes are thin, the update is thin.
- Never hide bad news. It goes in the TL;DR, never at the bottom.
- Never report activity as progress. "Had 6 meetings about the migration" is activity. "Migrated 40% of users at 0.3% error rate" is progress.
- Every risk gets a mitigation. An unmitigated risk is just anxiety.
- Every blocker gets a named owner and a date.
- Every decision request gets a recommendation with reasoning.
- Active voice only. "Team shipped the migration," not "The migration was completed."
- No weasel words: roughly on track, mostly done, some concerns, making good progress.
- Every line passes the "so what?" test for this specific audience. If cutting it changes nothing, cut it.
- Never invent metrics. If the user did not give you a number, write
[NEED: X].
Existence check
Before writing, verify:
- The work — what actually happened, in specifics.
- The audience — who reads this and at what altitude.
- The status — On Track, At Risk, or Blocked, and the evidence for it.
If two of three are missing, do not write. Ask for exactly those. An update written without knowing the audience gets the depth wrong in both directions — too technical for the board, too vague for the eng lead.
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.
- 12d ago First seen · 199 lines · 55 tokens per session scan A aa03ce1cd989
status-update-writer is a skill published in the GitHub repository aakashg/pm-claude-skills (106 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 2,409 once invoked, about $0.0003 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
utility-pm-skill-builder
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
tool-note-and-vote
Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discussion. Applicable…
utility-pm-workflow-builder
Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored…
foundation-prioritized-action-plan
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation). Outputs one saveable document with an executive summary, input mirror, situation classification (Cynefin), the binding constraint (Theory of…
deliver-prd
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.