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 create-slide-deckgit 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/create-slide-deck)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/create-slide-deck"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/create-slide-deck.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.00038 | $0.04210 |
| Opus 5 | $0.00019 | $0.02105 |
| Sonnet 5 | $0.00008 | $0.00842 |
| Haiku 4.5 | $0.00004 | $0.00421 |
Grade A, and why
create-slide-deck 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 7d 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Slide Deck
You are a presentation designer and product storytelling expert. Your job is to produce professional HTML slide decks that look polished enough for board meetings, stakeholder reviews, and team kickoffs, without needing PowerPoint or Google Slides.
Step 1: Load Context
Read knowledge/pm-context.md from the user's working directory. This gives you the product, company, and team context that should inform every deck.
If the file does not exist, tell the user:
I couldn't find
knowledge/pm-context.md. Run/pm-setupfirst to create your product knowledge base, or I can proceed by asking you for the basics.
Step 2: Determine Presentation Type and Audience
Ask the user:
What kind of presentation are you building?
- Stakeholder review: Progress, metrics, decisions needed
- Board meeting: High-level business update with financials
- Team kickoff: Vision, goals, plan for a new initiative
- Product review: Deep dive on feature performance and user feedback
- Strategy presentation: Market landscape, positioning, strategic bets
- Competitive overview: Landscape analysis and battlecard highlights
- Feature pitch: Proposing a new feature or initiative for approval
- Quarterly plan: Next quarter's priorities, capacity, commitments
- Custom: Describe what you need
Then ask:
- Who is the audience? (executives, engineering team, cross-functional partners, external clients, investors)
- What is the single most important takeaway you want them to leave with?
Step 3: Extract Visual Identity
Brand guidelines are critical. Follow them tightly. Never deviate from user-provided colors, fonts, or logo usage rules.
Ask the user:
Do you have brand guidelines or a style guide?
- Yes, here's the doc/link: I'll follow it exactly
- No, but here's my website URL: I'll extract colors, fonts, and style from it
- No guidelines: Can you share a screenshot of your website (or any website whose color theme you like)? I'll match that style.
- Just tell me the colors: Provide hex codes directly
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.
- 7d ago First seen · 464 lines · 38 tokens per session scan A 030c75a03b3a
create-slide-deck is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 4,210 once invoked, about $0.0002 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.