Borrowing it
Nothing to install: this file belongs to KaiUweHella/figma-bridge-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/KaiUweHella/figma-bridge-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/KaiUweHella/figma-bridge-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/kaiuwehella/figma-bridge-mcp/agents-md)<a href="https://agentmods.dev/instructions/kaiuwehella/figma-bridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kaiuwehella/figma-bridge-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/kaiuwehella/figma-bridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kaiuwehella/figma-bridge-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.00534 | $0.00534 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
figma-bridge-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 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
Agent skills
Issue tracker
Implementation tickets are maintained as private local Markdown under docs-local/issues/; that directory is ignored by Git. See docs-local/docs/agents/issue-tracker.md.
Live acceptance fixtures
A fixture that reproduces one of the maintainer's real Figma files carries a
bare file key, component keys and real screen copy. Such fixtures and their
test files live under the Git-ignored docs-local/evals/, never in a tracked
path — evals/roundtrip/ is ignored for that reason. check:public-safety
passing is not evidence that this content may be committed: diff the staged
content for file keys and personal names before any commit, and never
git add -A without reading the added-file list first.
What matters is the file key and any access key or token, because those
address and unlock a file. A bare node or slide id does not: 12:34 identifies
nothing without the file it belongs to, so real ids in docs, comments and test
fixtures are fine. Prefer placeholders in illustrative examples anyway — an
example reads better when it is obviously an example — but do not treat a node
id as a secret.
Raw measurement logs, probe transcripts and handoff documents belong under
docs-local/ (docs-local/live-tests/, docs-local/handoffs/): not because
node ids are sensitive, but because that material is session bookkeeping rather
than something the repository should carry.
Triage labels
Use the canonical local triage vocabulary needs-triage, needs-info,
ready-for-agent, ready-for-human, and wontfix. After verified
implementation, the local lifecycle status is completed. See
docs-local/docs/agents/triage-labels.md.
Domain docs
This is a single-context repository: read the root CONTEXT.md and, when the maintainer-local workspace is present, the decision pages under docs-local/decisions/ and the records under docs-local/adr/ before changing a domain area. A new durable decision is recorded there. See docs-local/docs/agents/domain.md.
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 Changed · +22 lines · +317 tokens per session 80cd71fae913
- 6d ago Changed · +8 lines · +65 tokens per session 7834ad8871ed
- 9d ago First seen · 19 lines · 152 tokens per session scan A 8cfa43a667a9
figma-bridge-mcp AGENTS.md is an instructions file published in the GitHub repository KaiUweHella/figma-bridge-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 534 tokens to every session, about $0.0027 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 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.
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.