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/breadchaincoop/labor.fun/slideshow-decknpx skills add BreadchainCoop/labor.fun --skill slideshow-deckgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWhat 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.00069 | $0.01073 |
| Opus 5 | $0.00034 | $0.00536 |
| Sonnet 5 | $0.00014 | $0.00215 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
slideshow-deck 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slideshow decks (make + host, encrypted)
Build a slideshow as one self-contained HTML file, statically encrypt it,
and publish it to the org's decks repo so it's served as a live, password-
gated slideshow at https://<org>.github.io/decks/<slug>.html.
Why not Google Drive: Drive can't render HTML — a Drive link forces a download. Hosting on GitHub Pages opens the deck as a real slideshow in the browser. Always host decks this way.
1. Build the deck
Start from ${CLAUDE_SKILL_DIR}/deck-template.html (the house format: inline
CSS/JS, one <section class="slide"> per slide, keyboard + click nav, progress
bar). Copy it, fill in the content, restyle the :root palette if you like.
Keep it one self-contained file — no external assets, no build step.
cp ${CLAUDE_SKILL_DIR}/deck-template.html /tmp/deck.html
# …edit /tmp/deck.html: title, slides, palette…
2. Encrypt it (required — never publish plaintext)
The Pages URL is public, so every deck is password-gated with StatiCrypt (client-side AES, no server). Get the deck password from config — do not hardcode it (this skill ships in a public repo):
DECK_PASSWORDenv var, or- the KB config
decks/config.md(password:frontmatter), or - ask the user if neither is set.
The password is quarter-scoped and rotates every quarter. The
decks/config.md password: is the single source of truth for the current
quarter — always read it fresh; never reuse a password you remember from a prior
quarter. Every deck published in a given quarter MUST use that quarter's
password.
On quarter rotation (when someone sets a new password): (1) update
password: + quarter: in decks/config.md, (2) re-encrypt every existing
deck in the decks repo with the new password so the old one stops working,
and push, (3) announce the new password in the core channel — never commit it to
a repo.
cd /tmp
npx staticrypt deck.html -p "$DECK_PASSWORD" --short -d out # → out/deck.html
What ships with it
1 file 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.
- 2d ago First seen · 98 lines · 69 tokens per session scan A a3f0c5584484
slideshow-deck is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 1,073 once invoked, about $0.0003 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
embedded-captions
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet…
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
diagnostic-stem-delivery
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.
chengfeng-check-updates
剪辑环境的唯一管理者：就绪检查（skills 是否最新 → Runtime 是否配套）、Skills 更新激活、Runtime 安装与体检。用户说检查更新、安装剪辑环境、装播放器、检查剪辑环境、剪辑环境就绪了吗、配置转录凭证时使用；业务 Skill（剪口播/字幕/画面/导出）第 0 步也引用本 Skill 的就绪检查。不用于剪辑、字幕、画面、导出本身或项目数据迁移。.
cap_llm_inspect_image
How to inspect a local image with inspectimage.