figma-edit-mcp: Instructions file for Codex

AGENTS.md

figma-edit-mcp AGENTS.md is an instructions file for Codex, OpenCode from neozhehan/figma-edit-mcp. It costs 386 tokens per session, scanned A, original, MIT.

Repository instructions for an MCP server that reads, creates, and changes Figma designs through code. Figma is a collaborative design application for interfaces and visual layouts; MCP is a way for an agent to use connected tools.

In plain words
What is it for?
Guiding automated Figma edits, handling structured tool errors, and applying the server's required safety workflow.
Why use it?
They require the agent to discover the design before editing it and to respect safety checks for scope, names, and batches.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

This is neozhehan/figma-edit-mcp's own configuration. It tells Codex and OpenCode how to work on figma-edit-mcp 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-edit-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to neozhehan/figma-edit-mcp. 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/neozhehan/figma-edit-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/neozhehan/figma-edit-mcp

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-edit-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/neozhehan/figma-edit-mcp/agents-md.svg)](https://agentmods.dev/instructions/neozhehan/figma-edit-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/neozhehan/figma-edit-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/neozhehan/figma-edit-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 386 This file is loaded in full into every session.
When invoked 386 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.00386 $0.00386
Opus 5 $0.00193 $0.00193
Sonnet 5 $0.00077 $0.00077
Haiku 4.5 $0.00039 $0.00039

Measured 8d ago against content hash c6fe173e4d57, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

figma-edit-mcp 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 8d 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 · 19 lines

What it actually says

AGENTS.md — Using figma-edit-mcp from an AI agent

This server enforces hard safety constraints (scope locking, name verification, batch validation) that you cannot bypass, and it returns structured error codes you need to recover from. Do not operate blind — load the guidance before writing.

The full operational guide lives in one place and is delivered three ways; use whichever your host supports:

  • MCP resources (any client, zero setup): read figma-edit://guide/constraints, figma-edit://guide/error-playbook, figma-edit://guide/workflows, figma-edit://guide/tool-selection.
  • The figma-edit skill (Claude Code, Copilot, Codex, Cursor, Gemini, Antigravity, …): skills/figma-edit/SKILL.md and its references/.
  • In this repo: skills/figma-edit/references/constraints.md, error-playbook.md, workflows.md, tool-selection.md.

For the precise enforcement contract behind these constraints — the safety guarantees, the conditions they hold under, the residual risks, and the per-tool gate matrix — see SAFETY.md at the repo root.

Two rules to internalize before anything else:

  1. Discover before acting. Start every node workflow with a read (page_infonode_info); pass names back verbatim.
  2. The plugin can refuse you. Constraints are checked at execution time and return structured errors — plan calls to comply rather than retrying.

Installing or developing figma-edit-mcp? See README.md (install) and CONTRIBUTING.md (development).

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. 8d ago First seen · 19 lines · 386 tokens per session scan A c6fe173e4d57

Subscribe to this mod's changes

figma-edit-mcp AGENTS.md is an instructions file published in the GitHub repository neozhehan/figma-edit-mcp (9 stars, last pushed today), licensed MIT. It adds 386 tokens to every session, about $0.0019 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens