start

A command that starts a ThroughLine design-system project, including its local folder, project manifest, and Figma connection. A design system is a shared set of visual rules and reusable interface parts.

In plain words
What is it for?
Use it to create or inspect the local design-system workspace, write the design-system manifest, connect Cursor to Figma, and route existing projects to setup, audit, or retrofit work.
Why use it?
It prepares the environment before design work begins and checks whether an existing project should continue, be audited, or resume an earlier retrofit phase. This avoids starting with the wrong setup path.

Command for Cursor

Install

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.

agentmods
npx agentmods add commands/jrpease/throughline/start
Clone the repo
git clone --depth 1 https://github.com/jrpease/throughline

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 268 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00268
Opus 5 $0.00000 $0.00134
Sonnet 5 $0.00000 $0.00054
Haiku 4.5 $0.00000 $0.00027

Measured 2d ago against content hash fc56ad105e6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start 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.

adapters/cursor/.cursor/commands/start.md · 23 lines

What it actually says

This is the first step for building a design system with ThroughLine. The user invoked it explicitly, so begin immediately — do not invoke any brainstorming or planning skill first. There is nothing to brainstorm until the environment exists: the local working folder must be created and Figma must be connected before any design work can happen.

Invoke the figma-environment-setup rule now and follow it exactly. It will:

  1. Locate or create the project directory and scan what's already there.
  2. Create the local working folder and write the design-system.json manifest.
  3. Connect Cursor to Figma and verify the connection.

If design-system.json already exists in this folder, the setup skill will detect it and route the user to the right next step rather than starting over — let it make that call. That routing now covers brownfield systems too: an existing/mature repo or populated Figma file is sent to design-system-audit first, and an in-progress retrofit (retrofit.phase set) resumes at its phase via retrofit-planner — the setup skill makes that call.

Scale all explanation to the user's coding level. Assume they may be design-fluent but new to developer tooling, terminals, and API tokens.

Changes

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.

  1. 2d ago First seen · 23 lines · 0 tokens per session scan A fc56ad105e6d

Subscribe to this mod's changes

start is a command 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 268 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.