What is section-builder?

A development workflow for building one website section from a Figma design, a shared interface-design file. It follows the project's existing tokens, component structure, semantic HTML, typed properties, and spring-based motion rules.

Use it to fetch a Figma section's measurements and copy, map them to design tokens, build the section in the correct folders, add content through properties or mock data, and run the project's checks.

It keeps a section consistent with the rest of the application instead of treating the design as an isolated mockup. It also requires checking the result against the design and the project's verification rules.

section-builder — Agent for Claude Code by textura-agency

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.

Clone the repo

git clone --depth 1 https://github.com/textura-agency/next16-claude-starter

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/section-builder/github.svg)](https://agentmods.dev/agents/textura-agency/next16-claude-starter/section-builder)

Your own site

<a href="https://agentmods.dev/agents/textura-agency/next16-claude-starter/section-builder"><img src="https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/section-builder/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/textura-agency/next16-claude-starter/section-builder"><img src="https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/section-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 763 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00763
Opus 5.5	$0.00020	$0.00305
Sonnet 5.5	$0.00010	$0.00153
Haiku 4.5	$0.00005	$0.00076

Measured 1mo ago against content hash 2a1c52579025, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

section-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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

section-builder — 89% identical, 47 lines differ

.claude/agents/section-builder.md · 52 lines

How it starts

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

You build exactly one section, to this project's conventions, and you verify it before reporting back.

Read obsidian/workflows/ai-agent-guide.md first — the hard rules are not optional and several of them are unusual (springs only, no keyframes, three-tier tokens, routes delegate to views).

Your loop

Fetch the design. get_design_context for values and copy, get_screenshot for layout. Never build from a text description.
Map values to tokens before writing markup. Reuse existing tokens; add --raw-* + semantic pairs for genuinely new values, with a comment naming the Figma frame. Never hardcode.
Build the component(s) in the right folder — primitives to components/ui/, feature pieces next to the feature, the view assembles them. Typed interface ...Props, named export, under ~150 lines, semantic markup.
Animate with springs — Inview for reveals, SpringTrigger scrub for parallax, Hover for hover, the text engine for text. Semantic tag, never div. No CSS keyframes, no other library. In a first-screen section import the robot twins (@/components/common/robot-spring, robot-text, robot-inview, robot-hover) so crawlers get the copy at rest; below-fold text engines take lazy; every loop: reads useMotionOff(). Blur once per line, never per letter; reveal first-screen copy by transform/clip with opacity 1 (axe samples fades mid-way); per-frame motion scaled by dt.
Content via props. Mocks in src/data/mocks/ if there is no real data.
Phone: the phone frame built in flow (never every element absolutely positioned from a 390-wide frame), split headlines grouped per word (white-space: nowrap), scrollWidth === innerWidth at 320–430, scene boxes lvh and overlays dvh + safe area (mobile-device-qa).
Verify: .claude/scripts/verify.sh plus the judgement checks in qa-verify (on a running build: tools/qa/axe-sweep.mjs, tools/qa/resize-check.mjs, tools/qa/check-motion.mjs). Fix what you find, then re-run.

Read the full file on GitHub · 52 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.

1mo ago Changed · +11 lines 2a1c52579025
2mo ago First seen · 41 lines · 50 tokens per session scan A 457bd7d713b7

Subscribe to this mod's changes

section-builder is an agent published in the GitHub repository textura-agency/next16-claude-starter (145 stars, last pushed 23d ago), licensed Unlicense. It adds 50 tokens to every session and 763 once invoked, about $0.0002 per session on Opus 5.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.

Design and UX Frontend

section-builder next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
section-buildertextura-agency/next16-claude-starter	Agent	145	23d ago	Unlicense	A	50	Claude Code
ux-flow-auditorCharlesWiltgen/Axiom	Agent	1.3k	yesterday	MIT	A	43	Claude Code
canvas-create-screensmicrosoft/power-platform-skills	Agent	1.1k	yesterday	MIT	A	24	Claude Code
nw-ux-designernWave-ai/nWave	Agent	631	yesterday	MIT	A	31	Claude Code
designRune-kit/rune	Agent	88	2mo ago	MIT	A	35	Claude Code
mobile-ux-optimizerxbim08/awesome-claude-code-plugins	Agent	10	1mo ago	Apache-2.0	A	0	Claude Code
visual-reviewermukiwu/muki-ai-plugins	Agent	74	15d ago	none	A	52	Claude Code