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 psd401/psd-claude-plugins --skill slides-to-sitegit clone --depth 1 https://github.com/psd401/psd-claude-pluginsWrote 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/psd401/psd-claude-plugins/slides-to-site)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/slides-to-site"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/slides-to-site/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/psd401/psd-claude-plugins/slides-to-site"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/slides-to-site.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.00121 | $0.01097 |
| Opus 5.5 | $0.00048 | $0.00439 |
| Sonnet 5.5 | $0.00024 | $0.00219 |
| Haiku 4.5 | $0.00012 | $0.00110 |
Grade A, and why
slides-to-site scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `git`, `jq`, `curl`, and Node.js 20.9 or later with npm. 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.
Slides to site
Turns a Google Slides link into a live page at
https://psd401.ai/presentations/<slug>, with the deck embedded, a thumbnail
and a written summary.
The site's repository holds the detailed, current instructions, next to the code they describe. This skill gets a checkout and follows them, so the two cannot drift apart. If anything here disagrees with the repository's playbook, the playbook wins.
What you need
git,jq,curl, and Node.js 20.9 or later with npm.gh, signed in with write access topsd401/psd401.ai. Check withgh auth status.- Read access to the deck from the account you run as: the
gwsCLI (gws auth login -s slides,drive), or another Google Workspace tool that can read the Slides API and export Drive files.
If anything is missing, say what and stop before changing anything.
1. Get a checkout of the site
Use the first of these that applies:
-
$PSD401_AI_REPOis set: use that directory. -
The current directory is inside a checkout whose
originispsd401/psd401.ai(git remote get-url origin): use it. -
Otherwise clone one:
gh repo clone psd401/psd401.ai "$(mktemp -d)/psd401.ai"Clone the full history. The bundle's
log.mdis generated from it, and a shallow clone writes a wrong one.
Run npm ci in the checkout if node_modules/ is missing. Never commit on
whatever branch an existing checkout is on; the ship steps make a new branch.
2. Read the playbook
In the checkout, read these in full before starting:
AGENTS.md: the site's rules..claude/skills/psd401-publish/presentation.md: this task, step by step..claude/skills/psd401-publish/ship.md: branch, checks, PR, CI, merge, and the live check.
If presentation.md is not there, the checkout is out of date. Run
git fetch origin and read the files from origin/main
(git show origin/main:.claude/skills/psd401-publish/presentation.md).
If origin/main does not have them either, stop. Tell the person the site
repository does not carry the publish playbooks yet, and change nothing. Do
not work from memory or from this file alone: the playbook holds the checks
and the merge gate.
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.
- 14d ago Changed · -1 lines c0b5e6844130
- 25d ago Changed · -103 lines · +48 tokens per session 423e2ec56e49
- 1mo ago Changed 605af3799569
- 2mo ago First seen · 216 lines · 73 tokens per session scan A 7493043d9405
slides-to-site is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 121 tokens to every session and 1,097 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…