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/jrpease/throughline/token-sheet-buildernpx skills add jrpease/throughline --skill token-sheet-buildergit clone --depth 1 https://github.com/jrpease/throughlineWrote 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/jrpease/throughline/token-sheet-builder)<a href="https://agentmods.dev/skills/jrpease/throughline/token-sheet-builder"><img src="https://agentmods.dev/badge/skills/jrpease/throughline/token-sheet-builder.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.00000 | $0.02365 |
| Opus 5 | $0.00000 | $0.01182 |
| Sonnet 5 | $0.00000 | $0.00473 |
| Haiku 4.5 | $0.00000 | $0.00236 |
Grade A, and why
token-sheet-builder 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 5d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token sheet builder
Creates a polished visual reference of the design system's tokens and styles on a dedicated Figma page called Foundations. This is the artifact designers and stakeholders actually look at — so it must be beautiful and on-brand, not a utilitarian dump of swatches.
Live vs regenerated — set expectations clearly
Bind to variables wherever Figma allows so the sheet live-updates for those
properties: a color swatch bound to gray/50 (in _Color/Primitive) re-colors
automatically when that primitive changes; spacing/radius examples bound to the variables resize
automatically. But labels, hex/value text, token names, descriptions, and the
set of tokens shown (adding/removing tokens) are snapshots — they don't
auto-update. So tell the user plainly: "The swatches update live when you change
a value, but if you rename tokens, change descriptions, or add/remove tokens,
re-run this skill to refresh the page." The sheet is regenerable; re-running
refreshes the snapshot parts.
(Tie-in: when the sync skill runs after token changes, refreshing Foundations is a sensible companion step — the sheet and the synced code both reflect Figma.)
Prerequisites
Needs tokens in Figma (tokens.semanticBuilt true) and a live Figma connection.
If tokens don't exist, offer to run token-builder. If Figma isn't connected,
offer figma-environment-setup. Use the mechanism in figma.mechanism.
Before scripting any figma_execute, read
.throughline/references/figma-scripting.md. This sheet builds large
swatch/type grids — exactly the layouts that hit the two worst traps: the
resize() axis-lock (collapses a color grid or type-meta column to ~10px) and the
single-call layoutWrap = "WRAP" timeout on big grids (build manual rows or split
across calls instead). Also run the single-bridge-instance preflight before writing.
Execution model — sequential architect → figma-executor with model routing.
If your host supports subagent dispatch, plan the sheet layout once with one
architect dispatch (deep tier) — a lighter plan than token-builder's, since
the tokens already exist; it emits a stable-identifier layout spec (which
collections/sections, how much per-token detail) — then build the page with
figma-executor dispatches (balanced tier), strictly sequentially: preflight
figma_get_status, concurrency-1, WIP: frame + build-verify-then-replace with
a programmatic read-back (spot-check that the swatches resolved to their bound
variables via figma_get_variables, not just a screenshot), gated by a
reviewer visual pass. Route per
.throughline/references/agent-routing.md; never parallelize Figma
work. If your host has no subagent dispatch, build and verify the page inline,
sequentially, as the steps below describe.
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.
- 5d ago First seen · 177 lines · 0 tokens per session scan A 28786195f817
token-sheet-builder is a skill published in the GitHub repository jrpease/throughline (76 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,365 tokens. 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-30.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…