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/generous-corp/pulp/render-toolchain-updatenpx skills add Generous-Corp/pulp --skill render-toolchain-updategit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/render-toolchain-update)<a href="https://agentmods.dev/skills/generous-corp/pulp/render-toolchain-update"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/render-toolchain-update.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.00131 | $0.04050 |
| Opus 5 | $0.00066 | $0.02025 |
| Sonnet 5 | $0.00026 | $0.00810 |
| Haiku 4.5 | $0.00013 | $0.00405 |
Grade A, and why
render-toolchain-update 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 today.
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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update the matched render toolchain
This procedure expects ghapp and python3, and operates on
tools/deps/manifest.json, tools/scripts/fetch_skia_for_release.py, and
tools/scripts/fetch_v8_for_release.py.
Pulp's default is a milestone-matched, provider-validated set: the published
skia-builder release, the Dawn revision that Skia itself built from, and the V8
revision from the same Chromium milestone branch. Chromium's raw Skia/Dawn DEPS pins
may differ from the later published Skia branch head; that is valid only when the
v8-builder release records both generations, binds built_skia/built_dawn to the
published provider, and passes the combined provider-identity/ODR gate. v8-builder may also publish
newer weekly LKGR releases; those remain valid opt-in V8 choices, but they are not the
default pin for a milestone update.
Truth model
Keep these values distinct in notes and manifests:
skia: exact commit atrefs/heads/chrome/mNNNused by skia-builder.built_dawn: Dawn from that Skia commit's ownDEPS; this is the Dawn actually compiled into the Skia/Dawn artifacts.v8: V8 from Chromiumrefs/branch-heads/<branch>DEPS for milestone NNN, after recording Chromium's raw Skia revision separately from the provider generation validated by the matched release.dawn: Chromium's Dawn pin. It can differ frombuilt_dawn; record the mismatch. Do not claim all three are one identical Chromium DEPS tuple when it differs.
v8-builder/tools/milestone_pin.py resolves and enforces this contract. For example:
python3 ../v8-builder/tools/milestone_pin.py 153 \
--skia-release-tag chrome/m153 > /tmp/m153-render-lock.json
python3 -m json.tool /tmp/m153-render-lock.json
The result must have the requested milestone, skia_release_tag, exact Chromium
skia/v8/dawn SHAs, and exact built_skia/built_dawn provider SHAs. False
skia_matches_chromium or dawn_matches_chromium values are disclosed provenance,
not failures: acceptance instead requires validated_skia_release to equal the
active Skia version, built_skia/built_dawn to equal Pulp's active provider, every
asset's embedded pair to agree, and the combined provider-identity/ODR gate to pass.
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.
- today First seen · 281 lines · 131 tokens per session scan A 34785b5e7fdf
render-toolchain-update is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 4,050 once invoked, about $0.0007 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…