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 daddia/claude-for-strategy --skill deck-outlinegit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/deck-outline)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/deck-outline"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/deck-outline/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/daddia/claude-for-strategy/deck-outline"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/deck-outline.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.00049 | $0.00833 |
| Opus 5.5 | $0.00020 | $0.00333 |
| Sonnet 5.5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
deck-outline 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 2mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deck Outline
When to use
For consultants building a storyline-first, action-titled deck outline before slide design. Markdown outline only — hand off to presentation tools after approval.
What this skill does not do
- Does not build slides — outline only; pptx or design tools after approval.
- Does not invent narrative without governing thought — route to
narrative-builderif needed. - Does not rewrite source analysis — maps pyramid to slides.
Preconditions
| Input | If missing |
|---|---|
| Practice profile (slide title style, exhibits) | Proceed with action titles default; flag practice-setup |
| Governing thought / narrative | Ask to run narrative-builder first |
Provisional mode
Thin narrative: label structured first pass; flag slides that don't trace to key line.
Trust spine
- Confidence bands (
narrative-synthesis): High = every slide traces to key line; Medium = some exhibit TBD; Low = topic list without governing thought — flag. - Analytical Rigor: Every slide supports a key line point; cut or flag non-load-bearing slides.
- Escalation: Slide without key-line parent → flag or cut; board-final → gate + reviewer note.
Full rules: ../../references/trust-conventions.md.
Workflow
- Read practice profile for slide title style and exhibit conventions.
- Use
narrative-builderoutput if available; else ask to build narrative first. - Map pyramid: governing thought slide → key line slides → supporting evidence (one exhibit per slide).
- Action titles unless profile says descriptive.
- Note exhibit per slide without building it.
- So-what test per
minto-pyramid.md— cut non-load-bearing slides.
Output format
GOVERNING THOUGHT: [headline]
Slide 1 — [Action title]
Exhibit: [...]
Slide 2 — [Action title for key line point 1]
Exhibit: [...]
...
Flag slides that don't trace to a key line point.
Worked example
Input: Governing thought: "Mid-tier price increase destroyed volume — revert pricing." Three MECE key lines.
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.
- 2mo ago First seen · 91 lines · 49 tokens per session scan A 22280d8328c8
deck-outline is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 833 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
review
Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
visual-review
Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…
to-pr
Gate, push, and open a GitHub pull request on the repo's PR template, then watch CI.
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
debate
Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.