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 agentmods add skills/contextgo/contextgo/deck-from-reportnpx skills add contextgo/contextgo --skill deck-from-reportgit clone --depth 1 https://github.com/contextgo/contextgoWhat 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 | $0.00034 | $0.00507 |
| Opus 5 | $0.00017 | $0.00253 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
deck-from-report 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 2d 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.
What it actually says
Deck From Report
Use this skill when the user provides a long-form report or markdown document and wants a summary deck.
Read ../../docs/input-contracts.md, ../../docs/layout-recipes.md, and
../../docs/quality-checks.md before drafting.
Use when
- The input is a long-form report or structured markdown.
- The expected output is a presentation deck distilled from that report.
- The team wants citation-aware section coverage.
Do not use when
- The input is a short brief (use
deck-from-brief). - The input is a PDF document (use
pdf-to-deck). - The user wants a flat handout (use the PDF or infographic recipes).
Workflow
1. Extract the report skeleton
Identify the executive thesis, the 3 to 7 most load-bearing sections, the data tables worth visualizing, and the quotes worth surfacing as callouts.
2. Pick the recipe
Default to deck.report-summary. Switch to deck.exec-summary when the user
asks for a 5 to 8 slide condensed deck. Record the rejected alternatives.
3. Apply the theme
Resolve all theme tokens before drafting slide content. Honor any theme override the user provides.
4. Choose the export mode
Default to pptx-static. Use pptx-morph when the report contains narrative
arcs that materially benefit from Morph transitions. Delegate Morph builds to
morph-ppt per ../../docs/morph-integration.md.
5. Produce the artifact
- generate the slide flow with section attribution back to the source
- run pre-export QC
- write the export file plus
build-notes.md,assets.json, andfailures.json - preserve traceability between each slide and the report section that produced it
Output
- a deck artifact in the requested mode
- a build note that records the chosen recipe, theme, mode, and section attribution
- an asset inventory and a failure list
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.
- 2d ago First seen · 65 lines · 34 tokens per session scan A b8443cb8fd28
deck-from-report is a skill published in the GitHub repository contextgo/contextgo (54 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 507 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.