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/dmitriyyukhanov/claude-plugins/rendernpx skills add DmitriyYukhanov/claude-plugins --skill rendergit clone --depth 1 https://github.com/DmitriyYukhanov/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/dmitriyyukhanov/claude-plugins/render)<a href="https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/render"><img src="https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/render.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.00614 |
| Opus 5 | $0.00044 | $0.00307 |
| Sonnet 5 | $0.00018 | $0.00123 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
render 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Render — HTML Generation
Take a tour-spec.json and produce a single-file index.html. This skill is deterministic; the heavy lifting is in ${CLAUDE_PLUGIN_ROOT}/scripts/render.cjs.
Trigger phrases
- "render the tour"
- "regenerate the HTML"
- "update the embedded sources"
- Auto-dispatched at the end of
learning-guide:analyze
Inputs
- Spec path —
tour-spec.jsonlocation. Default: CWD; explicit path supported. - Output directory — defaults to the spec's parent dir.
Steps
-
Locate the spec. If the user provides a path, use it. Otherwise look for
tour-spec.jsonin CWD. If neither, ask the user where the spec is. Do NOT scan the entire repository. -
Confirm Node is available. Run
node --version. If exit code is non-zero, tell the user Node.js must be on PATH and stop. Do not attempt fallback rendering. -
Inspect overrides. Look for
<spec-dir>/.learning-guide/template.html. If present, ensuretour-spec.renderer.template_compatibility_versionmatches the<!-- template_compatibility_version: N -->declaration on the override's first line. If missing or mismatched, ask the user to fix it before rendering. -
Run the renderer.
node "${CLAUDE_PLUGIN_ROOT}/scripts/render.cjs" "<spec-path>"If
--output-diris needed, pass it explicitly. -
Surface output. On success, print the renderer's stdout summary verbatim. On non-zero exit, print stderr verbatim and offer the troubleshooting table from
references/renderer-cli.md. -
Confirm artifacts. Verify
index.htmlandREADME.mdexist with non-zero size. If anything expected is missing, surface the discrepancy — do not retry blindly.
Re-running from the shell
The user can re-render without involving Claude by running node "<plugin-root>/scripts/render.cjs" tour-spec.json.
When NOT to use this skill
- The user wants new content, not a re-render. Dispatch
learning-guide:analyzeinstead. - The spec does not exist yet. Dispatch
learning-guide:analyze.
What ships with it
2 files 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.
- 4d ago First seen · 53 lines · 88 tokens per session scan A 6235561c6bf4
render is a skill published in the GitHub repository DmitriyYukhanov/claude-plugins (7 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 614 once invoked, about $0.0004 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
seam-probe
This skill should be used when testing or debugging an embedded-runtime boundary exposed through a dynamically loaded C-ABI library or Unix-domain socket, including requests to inspect exports, exercise FFI callbacks, send framed messages, reproduce seam crashes or hangs, fuzz a boundary, or correlate probe output…
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
esp32-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO)…
output
Show or switch the Mac's audio output device (built-in speakers, AirPods, external displays, DACs). Use when the user asks where sound is playing, which output device is active, or wants audio routed to a different device.
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…