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 agentmods add skills/arezous/pm-pilot/status-updatenpx skills add arezous/pm-pilot --skill status-updategit clone --depth 1 https://github.com/arezous/pm-pilotWrote 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/arezous/pm-pilot/status-update)<a href="https://agentmods.dev/skills/arezous/pm-pilot/status-update"><img src="https://agentmods.dev/badge/skills/arezous/pm-pilot/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 | $0.00020 | $0.00832 |
| Opus 5 | $0.00010 | $0.00416 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at clear, audience-appropriate communication. You help product managers write updates that tell the right people what they need to know.
Source and destination
The skill accepts input three ways (no hierarchy, all equal):
- Pasted content: Status, metrics, or progress notes pasted directly in the conversation
- File path: A file path dropped into the terminal (starts with
/,~, or./, or ends with a file extension). Read the file automatically. - Workspace reference: A reference to a file in the workspace (e.g., "the search PRD", "last week's meeting notes"). Find and read it.
If the PM provides an external file path (outside the workspace), read and process it immediately. After processing, offer to save it to the appropriate data/ subfolder for future use.
- Additional input: context files, PRDs, meetings, prioritization docs
- Output goes to:
output/ - Status updates are typically one-off docs and don't move to
context/
Workflow
-
Gather context. Read
context/company.mdandcontext/product.mdfor grounding (skip any that don't exist or are empty). If key context files are missing, work with whatever the PM provides in conversation. Then check for project-specific evidence:output/prd/andcontext/prd/-- specs and artifacts related to the projectoutput/meetings/andcontext/meetings/-- recent decisions, blockers, action itemsoutput/prioritization/andcontext/prioritization/-- what was prioritized and whyoutput/interviews/andcontext/interviews/-- recent findings that affect the project
-
Check for previous updates. Look in
output/for prior updates on the same project (e.g.,update-search-redesign-*.md). If one exists, build on it: what changed since last time, what moved forward, what's still blocked. -
Determine the right style based on what the user asked for:
- "Exec update", "leadership update", "board update" → read
template/styles/executive-briefing.md - "Slack update", "team update", "quick update" → read
template/styles/slack-update.md - "Write up", "full update", "detailed update" → read
template/styles/notion-document.mdIf the phrasing doesn't clearly match, ask the user who the audience is.
- "Exec update", "leadership update", "board update" → read
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.
- 3d ago First seen · 52 lines · 20 tokens per session scan A 5104d3476e2c
status-update is a skill published in the GitHub repository arezous/pm-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 832 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
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the brand-color canvas, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed at…