figma-use: Instructions file for Codex

AGENTS.md

figma-use AGENTS.md is an instructions file for Codex, OpenCode from dannote/figma-use. It costs 1,763 tokens per session, scanned A, original, MIT.

A project guide for building and testing a tool that connects a command-line program directly to Figma, a design application, through Chrome's debugging interface.

In plain words
What is it for?
Use it when adding commands or Figma communication, running builds and integration tests, or checking that a feature is complete before committing.
Why use it?
It gives coding agents the project's structure, required Figma setup, test commands, and checklist so new work is less likely to miss code, tests, or documentation.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is dannote/figma-use's own configuration. It tells Codex and OpenCode how to work on figma-use itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything figma-use configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { sendCommand } from '../client.ts'.

Reuse

Borrowing it

Nothing to install: this file belongs to dannote/figma-use. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dannote/figma-use/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/dannote/figma-use

Made for: Codex, OpenCode.

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 figma-use AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dannote/figma-use/agents-md/github.svg)](https://agentmods.dev/instructions/dannote/figma-use/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/dannote/figma-use/agents-md"><img src="https://agentmods.dev/badge/instructions/dannote/figma-use/agents-md/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.

agentmods 80×15 button for figma-use AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/dannote/figma-use/agents-md"><img src="https://agentmods.dev/badge/instructions/dannote/figma-use/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,763 This file is loaded in full into every session.
When invoked 1,763 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01763 $0.01763
Opus 5.5 $0.00705 $0.00705
Sonnet 5.5 $0.00353 $0.00353
Haiku 4.5 $0.00176 $0.00176

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

Security

Grade A, and why

figma-use 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 2mo 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.

AGENTS.md · 221 lines

How it starts

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

Development Guide

Architecture

packages/
  cli/      # Citty-based CLI, 100+ commands
  plugin/   # RPC handlers (built on-demand by CLI via esbuild)

CLI communicates directly with Figma via Chrome DevTools Protocol (CDP). No proxy server, no manual plugin installation.

Build & Test

bun install
bun run build           # Build CLI bundle
bun test                # Run integration tests

# Figma must be running with:
open -a Figma --args --remote-debugging-port=9222

Feature Completion Checklist

When implementing a new feature, ensure ALL of these are done before committing:

1. Implementation

  • CLI command in packages/cli/src/commands/
  • RPC handler in packages/plugin/src/rpc.ts (if needed)
  • Export from packages/cli/src/commands/index.ts

2. Tests

  • Add test file in packages/cli/tests/commands/
  • Test happy path and edge cases
  • Run bun test to verify all tests pass

3. Documentation

  • CHANGELOG.md — add entry under ## [Unreleased] or new version section
  • README.md — update if it's a user-facing feature
  • SKILL.md — update if it changes how agents should use the tool
  • REFERENCE.md — update command reference if adding/changing commands

4. Review Before Commit

bun test                        # All tests pass?
bun run build                   # Build succeeds?
git diff                        # Review all changes
git diff --cached               # Review staged changes

Adding Commands

  1. Create packages/cli/src/commands/my-command.ts:
import { defineCommand } from 'citty'
import { sendCommand } from '../client.ts'
import { printResult } from '../output.ts'

export default defineCommand({
  meta: { description: 'My command' },
  args: {
    id: { type: 'string', required: true },
    json: { type: 'boolean', description: 'Output as JSON' }
  },
  async run({ args }) {
    const result = await sendCommand('my-command', { id: args.id })
    printResult(result, args.json)
  }
})

Read the full file on GitHub · 221 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. 2mo ago First seen · 221 lines · 1,763 tokens per session scan A 3517e4624b25

Subscribe to this mod's changes

figma-use AGENTS.md is an instructions file published in the GitHub repository dannote/figma-use (614 stars, last pushed 4mo ago), licensed MIT. It adds 1,763 tokens to every session, about $0.0071 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.

Related

figma-use AGENTS.md compared with instructions from other repositories

figma-use AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
figma-use AGENTS.mddannote/figma-useInstructions file6144mo agoMITA1,763Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode