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 modem-dev/sideshow --skill sideshow-termgit clone --depth 1 https://github.com/modem-dev/sideshowWrote 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/modem-dev/sideshow/sideshow-term)<a href="https://agentmods.dev/skills/modem-dev/sideshow/sideshow-term"><img src="https://agentmods.dev/badge/skills/modem-dev/sideshow/sideshow-term/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/modem-dev/sideshow/sideshow-term"><img src="https://agentmods.dev/badge/skills/modem-dev/sideshow/sideshow-term.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.00085 | $0.00917 |
| Opus 5.5 | $0.00034 | $0.00367 |
| Sonnet 5.5 | $0.00017 | $0.00183 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
sideshow-term 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sideshow-term guide # or: curl -s $SIDESHOW_URL/guide How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sideshow-term
The user keeps a live terminal visual surface open (sideshow-term watch). You
publish STML — an HTML-like markup — and it renders instantly as real
opentui components (boxes, borders, big ASCII text, styled text, lists, menus).
This is a higher-fidelity surface than the text you normally print.
Before your first publish
Fetch the markup contract once per session:
sideshow-term guide # or: curl -s $SIDESHOW_URL/guide
If SIDESHOW_URL is unset, the surface is at http://localhost:4243. If the
server is not running, start it: sideshow-term serve. If the
sideshow-term command is not on PATH but you are inside this repo, use
node sideshow-term/bin/sideshow-term.js ....
Publishing
Prefer MCP tools if connected (publish_snippet, update_snippet,
list_snippets). Otherwise use the CLI — session grouping is automatic:
sideshow-term publish sketch.stml --title "Cache layout" --session-title "Cache redesign"
echo '<h1>Done</h1><text>Migration applied.</text>' | sideshow-term publish - --title "Status"
Save the returned sessionId and snippet id. Iterate with
sideshow-term update <id> revised.stml (same card, new version) instead of
publishing near-duplicates — versions are kept. Preview without the viewer:
sideshow-term render sketch.stml.
To remove stale visuals before replacing a board, run sideshow-term clear for
the current session or sideshow-term clear --all for every session on the
surface.
Rules of thumb:
- On your first publish, set a session title that names the task ("Auth refactor"), not the tool. It applies only when the session is created.
- One concept per snippet, with a clear title. A series of small snippets beats one giant page.
- Reach for
<card>,<row>/<col>,<list>,<bigtext>and the semantic color tokens (accent,success,danger,warning,info,muted) before hand-tuning layout.
Writing STML
Block tags: box row col card text h1 h2 h3 list/item hr spacer bigtext code select input. Inline tags (inside <text>/headings): b i u s dim color/c kbd badge a br. Layout attributes on blocks: width height padding margin gap direction align justify grow border border-style border-color bg title.
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 · 90 lines · 85 tokens per session scan A 72af88417e94
sideshow-term is a skill published in the GitHub repository modem-dev/sideshow (623 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 917 once invoked, about $0.0003 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-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…
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…