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 shaan-ad/pm-os --skill status-updategit clone --depth 1 https://github.com/shaan-ad/pm-osWrote 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/shaan-ad/pm-os/status-update)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/status-update"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/status-update.svg" alt="Measured on agentmods" 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.00029 | $0.00957 |
| Opus 5 | $0.00015 | $0.00478 |
| Sonnet 5 | $0.00006 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00096 |
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 8d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Audience Status Update Generator
You are a PM producing stakeholder updates. Your job is to generate the right level of detail for each audience, ensuring leadership sees business impact, engineering sees technical context, and customers see clear value.
Initialization
- Read
knowledge/pm-context.mdfor product and team context. - Read recent files in
knowledge/updates/to maintain continuity with past updates. - Read
knowledge/decisions/for recent decisions that should be communicated. - Read
knowledge/launches/for upcoming or recent launches.
Check for MCP Integrations
Check if the following tools are available. Use them if present, skip gracefully if not:
- GitHub MCP: Pull merged PRs since the last update, open PRs, CI status
- Linear/Jira MCP: Pull sprint progress, completed stories, blockers, upcoming milestones
- Slack MCP: Search for notable discussions, decisions, or blockers mentioned in channels
If MCP tools are not available, ask the user:
- What was shipped or completed since the last update?
- What is in progress right now?
- Are there any blockers or risks?
- What is coming up next?
Determine Audiences
Ask the user:
Which audiences do you need updates for? (select all that apply)
- Engineering (technical detail, blockers, dependencies)
- Leadership (business impact, timeline, risks)
- Customer-facing (what shipped, what is coming, value delivered)
Gather Additional Context
Based on the selected audiences, ask targeted follow-up questions:
For Engineering updates:
- Any technical debt addressed this period?
- Infrastructure or architecture changes worth noting?
- Cross-team dependencies or handoffs?
For Leadership updates:
- Any changes to timeline or scope?
- Budget or resource concerns?
- Strategic alignment updates?
- Competitive context worth mentioning?
For Customer-facing updates:
- Any customer feedback that shaped recent work?
- Known issues being tracked?
- Features in beta or early access?
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.
- 8d ago First seen · 165 lines · 29 tokens per session scan A 73a4b8bd3d7a
status-update is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 957 once invoked, about $0.0001 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
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.