reference-interpreter

reference-interpreter is a skill for Claude Code, Codex from senlindesign/claude2figma. It costs 58 tokens per session (606 once invoked), scanned A, original, MIT.

A design-reference analyzer turns a screenshot, image, URL, or design description into a structured design brief linked to reusable visual settings such as colors, typography, spacing, and layout.

In plain words
What is it for?
It helps document page structure, text hierarchy, colors, spacing, visual focus, and visible interface elements, then waits for confirmation before building.
Why use it?
It helps translate visual impressions into specific design decisions and highlights missing settings before new work is created.

Skill for Claude CodeCodex

Part of the claude2figma plugin — 4 skills, 1 hook shipped together

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 skills/senlindesign/claude2figma/reference-interpreter
Any agent
npx skills add senlindesign/claude2figma --skill reference-interpreter
Clone the repo
git clone --depth 1 https://github.com/senlindesign/claude2figma

Made for: Claude Code, Codex.

Or install claude2figma, the plugin that ships this one along with the rest of its 4 skills, 1 hook.

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

agentmods badge for reference-interpreter

README.md
[![agentmods](https://agentmods.dev/badge/skills/senlindesign/claude2figma/reference-interpreter.svg)](https://agentmods.dev/skills/senlindesign/claude2figma/reference-interpreter)
Your own site
<a href="https://agentmods.dev/skills/senlindesign/claude2figma/reference-interpreter"><img src="https://agentmods.dev/badge/skills/senlindesign/claude2figma/reference-interpreter.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 606 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.00058 $0.00606
Opus 5 $0.00029 $0.00303
Sonnet 5 $0.00012 $0.00121
Haiku 4.5 $0.00006 $0.00061

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

Security

Grade A, and why

reference-interpreter 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.

.claude/skills/reference-interpreter/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reference Interpreter

Analyze a reference (screenshot, URL, or description) and produce a Design Brief that maps visual observations to design system tokens. Output the Brief, then stop and wait for user confirmation before building anything.

Prerequisite: figma-preflight should have run so the Token Map and Style Registry are available.


Phase 1 — Analyze

Examine the reference across these dimensions:

  1. Layout — structure, columns, section heights, grid width, alignment
  2. Typography — heading/body hierarchy, weight contrast, tracking
  3. Color — dark/light sections, accent usage, neutral dominance
  4. Spacing — generous vs compact, section padding, internal gap
  5. Visual Anchor — what draws the eye: large type, hero image, illustration
  6. Components — what UI elements are visible: cards, buttons, forms, nav

Phase 2 — Map to Design System

For each observation, identify the specific Token or Style from the session's Token Map:

"Large dark headline" → Text Style: heading/h1 · Color: text/primary
"Neutral section bg"  → Variable: background/surface-2
"Tight card spacing"  → Gap: gap/xs · Padding: padding/sm

If no token exists, flag it:

⚠️ Gap: [observation] — no matching token. Options: (a) nearest match: [name], (b) add token first.

Phase 3 — Output the Design Brief

## Design Brief

**Reference**: [source]
**Section**: [what this covers]
**Aesthetic**: [3-5 keywords]

### Layout
[structure, height, alignment]

### Typography
- Heading: [Style name] — [why]
- Body: [Style name]

### Colors
- Background: [Variable] — [context]
- Text: [Variable]
- Accent: [Variable] — [used for]

### Spacing
- Section padding: [Variable]
- Internal gap: [Variable]

### Components needed
- [Name]: [from library? source]

### Gaps
- [Gap description] — awaiting decision
- (none) [if all mapped]

Phase 4 — Wait

Output exactly:

Brief complete. Type `confirmed` to begin building, or tell me what to adjust.

Read the full file on GitHub · 89 lines

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. 5d ago First seen · 89 lines · 58 tokens per session scan A 3f9a06f191aa

Subscribe to this mod's changes

reference-interpreter is a skill published in the GitHub repository senlindesign/claude2figma (198 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 606 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories