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 instructions/punkadillo/figma-code-composer/agents-mdgit 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/instructions/punkadillo/figma-code-composer/agents-md)<a href="https://agentmods.dev/instructions/punkadillo/figma-code-composer/agents-md"><img src="https://agentmods.dev/badge/instructions/punkadillo/figma-code-composer/agents-md.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.1 | $0.01472 | $0.01472 |
| Opus 5 | $0.00736 | $0.00736 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
figma-code-composer AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Drop-in scaffold for a Figma-driven multi-agent code-generation pipeline. Not a conventional app — it ships agents, prompts, hooks, protocols, and adapters that Claude Code and Cursor consume. Canonical project description: CLAUDE.md. This file gives contributors operating guidelines.
Project structure
| Path | Purpose |
|---|---|
.figma-pipeline/config.json |
Runtime config (created by wizard). Source of truth every agent reads. |
.figma-pipeline/config.schema.json |
JSON Schema; hard-pinned version: "1.0". |
.figma-pipeline/config.example.json |
Reference config — React + Tailwind v4 + Atomic Design. |
.figma-pipeline/protocols/ |
Cross-tool data contracts (manifest, token-strategy, component-layout, allowlist, skills, complexity, knowledge-graph, handover, cli). |
.figma-pipeline/adapters/{frameworks,css,design-systems}/<name>.md |
Per-stack code-gen templates. |
.figma-pipeline/skills/ |
Canonical skill catalog (~137 skills). Tool-neutral; both tools read via per-tool surfaces. |
.claude/{agents,commands,hooks}/ |
Claude Code surface (11 agents, 5 commands, 9 hooks). Per-tool skill surface (.claude/skills/<name> symlinks → canonical) is wizard-generated at /init-figma-compose. |
.cursor/{prompts,rules}/ |
Cursor mirror (10 .mdc rules + 11 agent prompts + 5 slash-command prompts + rules/README.md index). |
Keep matching files aligned across .claude and .cursor whenever behaviour changes.
Build, test, dev commands
No app build. Pipeline is exercised via the wizard + figma slash commands:
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.
- 2d ago First seen · 95 lines · 1,472 tokens per session scan A d4692fb1e137
figma-code-composer AGENTS.md is an instructions file published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 17d ago), licensed MIT. It adds 1,472 tokens to every session, about $0.0074 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-09-03.
Other instructions, from other repositories
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.
agent-template CLAUDE.md
Instructions for Zwanan-github/agent-template: Please follow the repository-wide agent instructions in AGENTS.md.
Clew AGENTS.md
Instructions for npatten/Clew, covering guidelines, resources, software development, design discipline and code organization.
lunge AGENTS.md
AGENTS.md instructions for thuupx/lunge, covering agents.md, what this is, token optimization features, import tools (param reference) and multi-step collection workflow.
abcd GEMINI.md
Gemini CLI instructions for intentdriven/abcd, a project described as: abcd: An experimental configuration layer for intent-driven development.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).