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.
curl -O https://raw.githubusercontent.com/neozhehan/figma-edit-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/neozhehan/figma-edit-mcpWrote 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/neozhehan/figma-edit-mcp/agents-md)<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/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.
<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="Reviewed on agentmods" width="80" 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.00386 | $0.00386 |
| Opus 5.5 | $0.00154 | $0.00154 |
| Sonnet 5.5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00039 | $0.00039 |
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 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.
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-editskill (Claude Code, Copilot, Codex, Cursor, Gemini, Antigravity, …):skills/figma-edit/SKILL.mdand itsreferences/. - 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:
- Discover before acting. Start every node workflow with a read (
page_info→node_info); pass names back verbatim. - 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).
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 First seen · 19 lines · 386 tokens per session scan A c6fe173e4d57
figma-edit-mcp AGENTS.md is an instructions file published in the GitHub repository neozhehan/figma-edit-mcp (14 stars, last pushed 8d ago), licensed MIT. It adds 386 tokens to every session, about $0.0015 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-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.