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 shawnstack/quickforge --skill presentationsgit clone --depth 1 https://github.com/shawnstack/quickforgeWrote 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/shawnstack/quickforge/presentations)<a href="https://agentmods.dev/skills/shawnstack/quickforge/presentations"><img src="https://agentmods.dev/badge/skills/shawnstack/quickforge/presentations/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/shawnstack/quickforge/presentations"><img src="https://agentmods.dev/badge/skills/shawnstack/quickforge/presentations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00931 |
| Opus 5.5 | $0.00017 | $0.00372 |
| Sonnet 5.5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
presentations 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentations skill
Use this skill to create or improve presentation deliverables. A good deck is not just text split across slides: it has a clear audience, narrative arc, slide-level purpose, visual hierarchy, and a practical speaking or reading flow.
This QuickForge adaptation intentionally does not depend on Codex cache paths, Codex workspace dependencies, or @oai/artifact-tool. Prefer Markdown slide outlines, speaker notes, and deck specs first. If the user explicitly needs PPTX generation, explain the available local workflow and ask before using shell commands or external tools.
When to use
Use this skill for requests involving:
- New slide decks, pitch decks, executive updates, board decks, sales decks, training decks, lecture decks, or conference talks.
- Slide outlines, storyboards, speaker notes, talk tracks, or visual direction.
- Reviewing or rewriting existing deck content.
- Turning a report, notes, transcript, or dataset into a presentation.
- PPTX-oriented deliverables where the first output can be a precise deck blueprint.
Deck principles
- Audience first. Determine who the deck is for and what decision or understanding it should drive.
- One main idea per slide. Each slide should have a clear takeaway title.
- Narrative arc. Use a logical flow: context → problem → insight → recommendation → next steps.
- Visual hierarchy. Prefer concise text, meaningful grouping, and clear emphasis.
- Evidence and action. For business decks, tie claims to evidence and end with actionable next steps.
- Readable density. Executive decks can be denser than live talks; live talks need fewer words and stronger speaker notes.
- Consistency. Keep terminology, structure, and visual patterns consistent across slides.
Recommended workflow
New presentation
- Identify audience, purpose, desired length, tone, and delivery mode.
- Create a deck outline with slide titles and slide objectives.
- Draft slide-by-slide content:
- Slide title as takeaway.
- Key bullets or content blocks.
- Suggested visual.
- Optional speaker notes.
- Check flow and remove redundancy.
- If writing to disk, create a Markdown deck spec or outline file unless the user requested another format.
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 · 112 lines · 43 tokens per session scan A 0688c9b8a19a
presentations is a skill published in the GitHub repository shawnstack/quickforge (45 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 931 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-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.