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/7nohe/figdeck/agents-mdgit clone --depth 1 https://github.com/7nohe/figdeckWhat 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 | $0.00579 | $0.00579 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
figdeck 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 yesterday.
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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Modules
- Root uses Bun workspaces. Code lives under
packages/withcli(Markdown → Figma Slides CLI, WebSocket server) andplugin(Figma plugin bundle withcode.ts+ui.html). Tests sit inpackages/cli/src/*.test.ts. Reference Markdown samples inexamples/, docs source inpackages/docs/src/content/docs/. Build outputs land in each package’sdist/.
Build, Test, and Development Commands
- Install deps:
bun install. - Build all packages:
bun run build(runs tsup for the CLI and esbuild for the plugin). - Dev/watch:
cd packages/cli && bun run devfor the CLI;cd packages/plugin && bun run watchfor plugin reloads. - Type-check everything:
bun run typecheck. - Lint/format via Biome:
bun run lint(check),bun run format(write). Prefer format before committing. - Tests:
cd packages/cli && bun test(usesbun:test; mirrors the*.test.tsfiles insrc/).
Coding Style & Naming Conventions
- TypeScript with ES modules. Follow Biome defaults: 2-space indentation, double quotes, required semicolons. Config lives in
biome.json. - Keep CLI utilities pure and reusable under
packages/cli/src/; add WebSocket-facing code inws-server.ts. - Use
camelCasefor functions/variables,PascalCasefor types/interfaces, andkebab-casefor file names.
Testing Guidelines
- Add
*.test.tsalongside the logic inpackages/cli/src/; prefer unit tests with clear inputs/outputs (e.g., color normalization, gradient parsing). - When touching parsing or rendering rules, include edge cases (whitespace, shorthand colors, gradient angles). Avoid relying on network/Figma in tests.
- Run
bun testplusbun run lintbefore opening a PR.
Commit & Pull Request Guidelines
- Commit messages: short, imperative summaries; prefix with a scope when helpful (e.g.,
feat:,fix:,chore:). Keep changes cohesive per commit. - Pull requests: include a concise description, testing notes (commands run), and link related issues. For plugin UI/visual tweaks, attach a screenshot or brief demo steps. Ensure builds succeed (
bun run build) before requesting review.
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.
- yesterday First seen · 30 lines · 579 tokens per session scan A 93e82ac045a9
figdeck AGENTS.md is an instructions file published in the GitHub repository 7nohe/figdeck (4 stars, last pushed 8mo ago), licensed MIT. It adds 579 tokens to every session, about $0.0029 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
slide-mcp copilot-instructions.md
Copilot instructions for Rikuto-des/slide-mcp, covering slide-mcp — copilot instructions, generating a deck, layouts (slide.layout), design systems (theme.preset) and minimal example.
figwright AGENTS.md
Instructions for awdr74100/figwright, covering agents.md, architecture, layout, tech stack and commands.
figwright CLAUDE.md
Instructions for awdr74100/figwright: Read AGENTS.md first — it's the single source of guidance for this repo: architecture, layout, tech stack, commands, conventions, release flow, and gotchas.
FigCC AGENTS.md
Instructions for madebypan/FigCC, covering agents.md, project identity, runtime architecture, security invariants and compatibility and storage.
FigCC CLAUDE.md
Instructions for madebypan/FigCC, covering claude.md and claude-specific runtime note.
figma-mcp-free copilot-instructions.md
Instructions for karthikyaddana/figma-mcp-free, covering figma mcp free rules, required flow (do not skip), implementation rules, tool usage guide and node id format.