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-sync-layernpx skills add jrpease/throughline --skill token-sync-layergit clone --depth 1 https://github.com/jrpease/throughlineWhat 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.03996 |
| Opus 5 | $0.00000 | $0.01998 |
| Sonnet 5 | $0.00000 | $0.00799 |
| Haiku 4.5 | $0.00000 | $0.00400 |
Grade A, and why
token-sync-layer 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 3d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Token sync layer
Compiles Figma variables into code. The pipeline is one-directional — Figma is the source of truth for token values; code consumes generated artifacts that are never hand-edited:
Figma variables → DTCG JSON → Style Dictionary → adapter output (per platform)
This skill both performs the sync and installs the reusable /sync-figma-tokens
command so the user can re-run it anytime tokens change.
Calibrate
Read user.codingLevel (.throughline/references/coding-level.md) and scale explanation
accordingly. The pipeline involves several developer concepts (JSON, build
tools, PRs) — for new users, explain each plainly the first time; for
comfortable users, be terse. Actions are identical across levels.
Prerequisites (offer to run them, don't bail)
Read the manifest. This skill needs two things:
- Tokens in Figma —
tokens.semanticBuiltshould be true. If no tokens exist, offer to runtoken-builderfirst. - At least a local git repo —
workspace.stagemust belocal-gitorgithub(so the sync can land changes as a reviewable diff/PR). If it's stillfolder, this is the soft-nudge seam: offer to runrepository-builderto add version history first. Explain plainly why ("the sync writes code files, and git lets you review exactly what changed before keeping it"). If the user is atlocal-gitbut notgithub, strongly recommend connecting a remote (GitHub or similar) so the sync can land as a real reviewable PR — the cleanest review model — but don't force it; a reviewed branch diff works atlocal-git.
A live Figma connection is also required — do a cheap liveness read; if it
fails, offer figma-environment-setup.
Step 1 — Choose target platform(s)
Ask which platform(s) the user is building for. Read
.throughline/references/sync-adapters.md for the two-tier adapter model.
- Curated (Tier 1):
shadcn,tailwind,mui,vanilla-css,ios-swift. Vetted presets — high confidence. - Generated (Tier 2): any other framework (Ant Design, Chakra, HeroUI, Android/Kotlin, Flutter, etc.). The skill generates an adapter and verifies it against a real component before trusting it.
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.
- 3d ago First seen · 300 lines · 0 tokens per session scan A 8312fa6ed479
token-sync-layer is a skill published in the GitHub repository jrpease/throughline (76 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,996 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…