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 P47Phoenix/Claude-Plugins --skill presentationgit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/presentation)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/presentation"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/presentation/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/p47phoenix/claude-plugins/presentation"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/presentation.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.00114 | $0.02683 |
| Opus 5.5 | $0.00046 | $0.01073 |
| Sonnet 5.5 | $0.00023 | $0.00537 |
| Haiku 4.5 | $0.00011 | $0.00268 |
Grade A, and why
presentation 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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Composer
Design Principle: Compose, Don't Create
This skill is a mini-orchestrator, not a content creator. The Composer assembles contributions from delivery team roles (PO, Data Analyst, Developer, Architect, QA) into a cohesive presentation. Each contributing role loads its own skill to produce domain-accurate content. The Composer shapes tone, flow, density, and format — the team creates the content.
Context isolation: Contributing roles run as sub-agents with only their relevant artifacts. The Composer reads their draft outputs from disk. No role's full context leaks into another.
Signal: SKILL_LOADED: presentation
Phase 1: Type Detection
Detect type from user request using keyword matching. If ambiguous, ask — never guess.
| Type | Keywords | Detail |
|---|---|---|
| Sprint Review | "sprint review", "what we delivered", "sprint demo", "end of sprint" | references/types/sprint-review.md |
| Feature Pitch | "pitch", "propose", "sell this feature", "why we should build" | references/types/feature-pitch.md |
| Stakeholder Update | "status update", "executive update", "progress report", "stakeholder" | references/types/stakeholder-update.md |
| Technical Deep-Dive | "technical presentation", "architecture overview", "deep dive", "how it works" | references/types/technical-deep-dive.md |
| Investor Pitch | "investor pitch", "fundraising deck", "pitch to investors" | references/types/investor-pitch.md |
| Roadmap | "roadmap", "quarterly plan", "what's coming next" | references/types/roadmap.md |
| Product Demo | "product demo", "feature demo", "show what we built", "demo for publisher" | references/types/product-demo.md |
| Onboarding | "onboarding", "project handoff", "team orientation", "getting started" | references/types/onboarding.md |
| Retrospective Summary | "retro summary", "retrospective presentation", "what we learned" | references/types/retrospective-summary.md |
Pipeline Auto-Detection (when type not explicit)
What ships with it
24 files 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.
- references/data-visualization.md 5.2 KB
- references/flow/assemble.md 1.0 KB
- references/flow/compose.md 8.4 KB
- references/flow/content-gate.md 1.7 KB
- references/flow/draft.md 1.6 KB
- references/flow/review-gate.md 1.6 KB
- references/flow/user-review.md 3.1 KB
- references/formats/marp.md 426 B
- references/formats/paste-ready.md 333 B
- references/formats/pptx.md 805 B
- references/formats/structured-markdown.md 372 B
- references/marp-templates.md 4.3 KB
- references/narrative-patterns.md 23 KB
- references/slide-structure.md 11 KB
- references/types/feature-pitch.md 512 B
- references/types/investor-pitch.md 562 B
- references/types/onboarding.md 758 B
- references/types/product-demo.md 811 B
- references/types/retrospective-summary.md 1.1 KB
- references/types/roadmap.md 683 B
- references/types/sprint-review.md 557 B
- references/types/stakeholder-update.md 521 B
- references/types/technical-deep-dive.md 505 B
- scripts/generate_pptx.py 15 KB runs code
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 · 186 lines · 114 tokens per session scan A eaf280c2c857
presentation is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 114 tokens to every session and 2,683 once invoked, about $0.0005 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-09-03.
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.