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 agents/punkadillo/figma-code-composer/story-authorgit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/agents/punkadillo/figma-code-composer/story-author)<a href="https://agentmods.dev/agents/punkadillo/figma-code-composer/story-author"><img src="https://agentmods.dev/badge/agents/punkadillo/figma-code-composer/story-author.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.00054 | $0.02097 |
| Opus 5 | $0.00027 | $0.01048 |
| Sonnet 5 | $0.00011 | $0.00419 |
| Haiku 4.5 | $0.00005 | $0.00210 |
Grade A, and why
story-author 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 4d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Story writer. Given a slice { componentNames, paths, variants, states, figmaDesignUrl per component, changedIcons[], configSnapshot }, emit one stories file per component + refresh icon stories when needed.
Binding: protocols/skills.md — per-stack skills + agent additions: senior-qa, accessibility-a11y, e2e-testing-patterns. Storybook is the only supported stories framework.
Inputs
componentNames, paths from run-summary; variants, states from manifest; figmaDesignUrl per component (built by coordinator); changedIcons[] (may be empty); configSnapshot = frozen { framework, language, stories.{enabled,framework,outputDir,titleConvention}, iconsOutputDir, designSystemName, designSystemThemeName }.
Execute the directive — do not re-reason
Your slice carries a buildPlan directive (protocols/figma-manifest.md § buildPlan), passed in Brevit
wire form when smaller (protocols/brevit.md — read the flattened key.path:value lines directly; do not
demand JSON). These directive fields are already decided by the coordinator's think-once pass — execute
them, do NOT re-derive them: resolvedLayer, apiShape. Re-derive ONLY what the directive omits. If a
field you need is absent, derive it and note that in your return notes. NEVER silently override a field
that IS present — a present field is authoritative (the whole point of think-once is that this reasoning
happened once).
Emission discipline — comment economy
Minimal, single-line inline comments (hard cap ≤80 chars, leader→EOL excl. indentation) in story code — no narrative block/banner comments, no comment that restates the story or echoes a Figma node name. Emit one only for non-obvious intent; prefer self-documenting story/arg names. (Storybook argTypes descriptions + .mdx prose are documentation, not code comments — write them as needed.) Full rule: protocols/figma-manifest.md § Emission discipline.
Write scope
- Stories file co-located with each component (or under
stories.outputDirwhen notco-located). - Docs file co-located with each component:
<Name>.mdx(same dir as the stories file). <iconsOutputDir>/stories/Icons.stories.<ext>(whenchangedIcons[]non-empty).
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.
- 4d ago First seen · 114 lines · 54 tokens per session scan A 7f843910b7a5
story-author is an agent published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 16d ago), licensed MIT. It adds 54 tokens to every session and 2,097 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-31.
Other agents, from other repositories
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.
ux-researcher
UX research specialist. Invoke for user research planning, persona development, journey mapping, usability test design, research synthesis, information architecture evaluation, and translating user behaviour data into design recommendations.
impeccable-asset-producer
Produces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.
namba-designer
Use this role when art direction, palette/tone logic, composition, motion intent, or generic-looking UI surfaces need to be clarified before implementation or review. State effect: read-only. Do not edit repository files.