Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ApurvBazari/claude-plugins/plugin install walkthroughWrote 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/apurvbazari/claude-plugins/render)<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/render"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/render/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/apurvbazari/claude-plugins/render"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/render.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.00060 | $0.00656 |
| Opus 5.5 | $0.00024 | $0.00262 |
| Sonnet 5.5 | $0.00012 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
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 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Render — Assemble a Supplied Model into the House Style
You are invoked by a caller (e.g. the lens plugin) that has already synthesized a model in
context. You are the programmatic entry for the terminal render stages: skip gather + synthesize
and run only select → assemble → self-check → write. The model conforms to
../create/references/session-model.md (review fields allowed).
references/render-contract.md is the canonical description of those four shared stages (it is the
same select → assemble → self-check → write every producer ends on) plus the review-specific assembly
(findings[] → sheets, diffHunks[], adherence, verdict). Follow it for the render half.
Step 1: Locate the model + output path
The caller passes (a) a structured model in context and (b) an output path argument. If NO model is present in context, stop and tell the user: "Nothing to render — use /walkthrough:create for a session recap." Never synthesize from the transcript here.
Step 2: Run the shared render stages
Run select → assemble → self-check → write exactly as described in references/render-contract.md,
including its § Review-specific assembly for findings/diffHunks/adherence. Write to the
caller-supplied output path (create the directory if missing); do not prompt for gitignore (the caller
owns its output location). Return the written path to the caller.
When the page has a system map, run the contract's insert the system-map engine step after the
write, and its check. The engine file is
${CLAUDE_PLUGIN_ROOT}/skills/create/references/system-map-engine.js (the same file as
${CLAUDE_SKILL_DIR}/../create/references/system-map-engine.js). Return the contract's
System map engine: … line to the caller with the path.
Key Rules
- Internal only.
user-invocable: false; callers invoke it via the Skill tool. - No synthesis. Render the supplied model verbatim — never re-derive from the transcript.
- Follow the contract. The shared stages + review assembly live in
references/render-contract.md; this skill is their programmatic entry point, not a second copy of them. - Self-contained + tokens only. Same invariants as create; run the structural self-check before write.
- Engine by the contract. A page with a system map gets its engine through the contract's insert step; never return a page that still holds the marker line.
- Empty context → redirect to create. Never silently fall back to synthesis.
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 Changed · +7 lines 80cde60809ac
- 1mo ago First seen · 36 lines · 60 tokens per session scan A 1b6aa0a275ec
render is a skill published in the GitHub repository ApurvBazari/claude-plugins (1 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 656 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-31.
Other skills, from other repositories
c-notify
Send native macOS notification center alerts from the command line using terminal-notifier.
notifications
Send notifications through the unified notification router.
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.