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 davistroy/claude-marketplace --skill sg-outlinegit clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/sg-outline)<a href="https://agentmods.dev/skills/davistroy/claude-marketplace/sg-outline"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/sg-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/davistroy/claude-marketplace/sg-outline"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/sg-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.00037 | $0.00589 |
| Opus 5.5 | $0.00015 | $0.00236 |
| Sonnet 5.5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
sg-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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slide Generator: Outline Step
Generate a structured presentation outline from research findings. Uses Claude with extended thinking (budget_tokens=4096) to produce a well-organized slide structure.
Pre-loaded Context
Working directory:
!pwd
Available research files:
!ls -la *.json 2>/dev/null || echo "No JSON files found"
Prerequisites
- Preflight:
sg --versionmust succeed before proceeding — ifsgis missing, stop and tell the user this requires the privatedavistroy/slide-generatorengine (owner-only; see ADR-0008) slide-generatorpackage installedANTHROPIC_API_KEYset in environment- A
research.jsonfile from the research step (or equivalent structured JSON)
Input Validation
Required:
<research.json>- Path to research findings file
Optional:
--output <path>- Output file path (default:outline.json)--target-slides <N>- Target number of slides (default: 20, configurable viaSG_TARGET_SLIDES)--multi-presentation- Allow splitting into multiple presentations if content warrants it
Instructions
- Verify input: Confirm the research JSON file exists and contains valid structured data
- Run outline generation:
sg outline research.json --output outline.json - Verify output: Confirm
outline.jsonwas created with slide structure - Report results: Show the outline structure (slide titles, approximate slide count)
Error Handling
| Error | Cause | Fix |
|---|---|---|
File not found |
Wrong path to research.json | Check file path, list directory |
Invalid JSON |
Corrupted or incomplete research file | Re-run research step |
Token limit exceeded |
Research too large | Set SG_OUTLINE_MAX_TOKENS=16384 or reduce research scope |
Output
The outline step produces outline.json containing:
- Ordered list of slides with titles
- Bullet point structure per slide
- Speaker notes hints
- Graphics description placeholders
- Logical flow and transitions
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 · 72 lines · 37 tokens per session scan A b58ab8219704
sg-outline is a skill published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 589 once invoked, about $0.0001 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-04.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…