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 sananthanarayan/skilldrop --skill slide-outlinergit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote 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/sananthanarayan/skilldrop/slide-outliner)<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/slide-outliner"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/slide-outliner.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.00074 | $0.00912 |
| Opus 5 | $0.00037 | $0.00456 |
| Sonnet 5 | $0.00015 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
slide-outliner 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slide-outliner
You help the user plan a deck before they open PowerPoint, by producing a slide-by-slide outline with structure, key points, and speaker notes.
How to respond
-
Pin down audience + format + time.
- Audience: engineering peers? execs? customers? regulators? Mix?
- Format: live presentation (with discussion) vs. read-ahead doc vs. async share?
- Time: 10 minutes? 30? 60? — this determines slide count more than anything else.
Rough guide: 1.5–2 minutes per slide in a live setting with Q&A. So 30 minutes → 12–15 content slides max, including the cover and the close.
-
Default structure for an architecture review: see
templates/deck-outline.md. Sections in order:- Cover — title, presenter, audience, date
- Why we're here — the question/decision/approval being sought (one slide)
- Context — what's the current state, what changed, what's the forcing function (1–2 slides)
- Proposed approach — the architecture / decision / change (3–5 slides — this is the bulk)
- Alternatives considered — the strongest 1–2, and why we didn't pick them (1 slide each, max)
- Risks & mitigations — pick the 3–4 the audience cares most about (1 slide)
- Cost, timeline, rollout (1 slide)
- What we need from you — the Ask (1 slide)
- Appendix — backup slides for deep-dive questions (not part of the planned flow)
-
Per slide, produce:
- Slide title (a sentence that states the takeaway, not a category label — "Postgres meets our latency target" beats "Database evaluation")
- Key points (3–5 bullets — what's actually on the slide)
- Speaker notes (2–3 sentences — what the presenter says that isn't on the slide)
-
Plan for Q&A. Add an Appendix section with 3–5 "if they ask…" backup slides covering the topics most likely to come up:
- Cost detail / TCO
- Security & compliance
- Migration path / backwards compatibility
- Vendor risk / open-source health
- Why-not the obvious-but-rejected alternative
What ships with it
4 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.
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.
- 8d ago First seen · 59 lines · 74 tokens per session scan A 08972eeeb497
slide-outliner is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 24d ago), licensed MIT. It adds 74 tokens to every session and 912 once invoked, about $0.0004 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-31.
Other skills, from other repositories
readme
This skill should be used to audit OR elevate the README of a public repository. Trigger with "improve the README", "make the readme high quality", "elevate this readme", "audit the readme", "add badges", "is our README good", or before publishing/releasing a repo. Elevate rebuilds a thin/generic README to a polished…
cairn-attention
Resolve Cairn's pending-attention queue inline (DEC drafts, baseline findings, drift events).
cairn-direction
Spec-tightener + subagent dispatcher. Engage on code-change asks — verbs, bug reports, observations. Pivot-aware on active tasks.
cairn-resync
Operator-initiated re-discovery — resolve config drift, re-cluster topics, re-curate grown areas into DEC/INV drafts.
ship
Execute an approved pitch/spec as a delegated, closed-scope cycle with verification and adversarial review. Invoke it yourself with /ship — a cycle spawns a writer and opens a PR, so it starts when you say so. Enforces the execution playbook: right-size gate, pre-spawn filter, doc-bundle, PR format, review.
adr-new
Create a new Architecture Decision Record with append-only, status-gated supersession, and update the ADR index. Invoke with /adr-new, or let /tdd-author invoke it on approval of an ADR action (this skill stays model-invocable for that reason).