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 sethdford/claude-skills --skill stakeholder-presentationgit clone --depth 1 https://github.com/sethdford/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/sethdford/claude-skills/stakeholder-presentation)<a href="https://agentmods.dev/skills/sethdford/claude-skills/stakeholder-presentation"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/stakeholder-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/sethdford/claude-skills/stakeholder-presentation"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/stakeholder-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.00037 | $0.00671 |
| Opus 5 | $0.00018 | $0.00336 |
| Sonnet 5 | $0.00007 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
stakeholder-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 10d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Presentation
Present architecture effectively to diverse audiences with tailored messaging and engagement.
Context
You are presenting architecture to stakeholders. Tailor message for audience (executives care about cost/risk, engineers care about design). Anticipate objections. Manage time and questions.
Domain Context
Based on presentation and communication best practices:
- Executive Audience: Lead with business impact (revenue, cost, risk). 20% architecture, 80% business. Numbers matter.
- Technical Audience: Design tradeoffs, implementation details, scalability. Respectful skepticism.
- Product Audience: Impact on feature velocity, user experience, reliability. Timeline and risk.
- Presentation Skills: Structure, pacing, visuals, energy. Engage audience, read room.
Instructions
-
Tailor to Audience:
- Executives: "This microservices architecture reduces deployment risk by 90% and lets us deploy 5x faster, reducing time-to-market by 4 weeks."
- Engineers: "Services communicate via REST with circuit breakers, 3-second timeout, exponential backoff."
- Product: "Architecture enables us to deploy payment service independently, reducing feature dependencies."
-
Structure:
- Hook (why this matters)
- Problem (what's broken)
- Solution (how we fix it)
- Impact (revenue, cost, speed, reliability)
- Questions & Discussion
-
Visuals: Use diagrams (C4), not bullet points. Show architecture, data flow, scaling. One idea per slide.
-
Manage Q&A:
- Tough question? "Great question, I'll come back to that." (Gives you time to think)
- Don't know? "I don't know, but I'll find out and follow up."
- Skepticism? Acknowledge, address directly. "You're right, that's a risk. Here's how we mitigate it."
-
Follow-Up: Send summary and decision. Record decisions, next steps, owners.
Anti-Patterns
- One-Size-Fits-All Presentation: Same talk for executives and engineers. Result: one group lost, other bored. Guard: Customize per audience; keep different versions.
- Death by Bullet Points: 40 slides of text. Result: audience reads slides instead of listening. Guard: Visuals, not words; one idea per slide; speak, don't read.
- Defensive on Questions: Get flustered by skepticism. Result: lose credibility. Guard: Welcome tough questions; acknowledge valid concerns; address respectfully.
- No Follow-Up: Presentation ends, decision unclear, no next steps. Result: confusion, inaction. Guard: Summary email, clear decisions, owners, timeline.
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.
- 10d ago First seen · 58 lines · 37 tokens per session scan A 2b160075666f
stakeholder-presentation is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 671 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
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize…
lead-intelligence
AI-native lead intelligence and outreach pipeline. Replaces Apollo, Clay, and ZoomInfo with agent-powered signal scoring, mutual ranking, warm path discovery, and personalized outreach. Use when the user wants to find, qualify, and reach high-value contacts.
springboot-verification
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
team-builder
Interactive agent picker for composing and dispatching parallel teams.
cmd_aside
Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.
seo
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.