figdeck: Instructions file for Codex

AGENTS.md

figdeck AGENTS.md is an instructions file for Codex, OpenCode from 7nohe/figdeck. It costs 579 tokens per session, scanned A, original, MIT.

A repository instruction file for Figdeck, a Bun-based project that converts Markdown into Figma Slides using a command-line package and a Figma plugin.

In plain words
What is it for?
Use it when working in the CLI or plugin packages, building or watching the project, running type checks and tests, formatting code, or adding tests in the expected locations.
Why use it?
It gives coding agents the project structure, development commands, style rules, and testing expectations in one place.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 figdeck AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/7nohe/figdeck/agents-md"><img src="https://agentmods.dev/badge/instructions/7nohe/figdeck/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 579 This file is loaded in full into every session.
When invoked 579 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.00579 $0.00579
Opus 5.5 $0.00232 $0.00232
Sonnet 5.5 $0.00116 $0.00116
Haiku 4.5 $0.00058 $0.00058

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

Security

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 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 · 30 lines

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/ with cli (Markdown → Figma Slides CLI, WebSocket server) and plugin (Figma plugin bundle with code.ts + ui.html). Tests sit in packages/cli/src/*.test.ts. Reference Markdown samples in examples/, docs source in packages/docs/src/content/docs/. Build outputs land in each package’s dist/.

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 dev for the CLI; cd packages/plugin && bun run watch for 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 (uses bun:test; mirrors the *.test.ts files in src/).

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 in ws-server.ts.
  • Use camelCase for functions/variables, PascalCase for types/interfaces, and kebab-case for file names.

Testing Guidelines

  • Add *.test.ts alongside the logic in packages/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 test plus bun run lint before 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.

Read the full file on GitHub · 30 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 · 30 lines · 579 tokens per session scan A 93e82ac045a9

Subscribe to this mod's changes

figdeck AGENTS.md is an instructions file published in the GitHub repository 7nohe/figdeck (4 stars, last pushed 10mo ago), licensed MIT. It adds 579 tokens to every session, about $0.0023 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.

Related

figdeck AGENTS.md compared with instructions from other repositories

figdeck AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
figdeck AGENTS.md7nohe/figdeckInstructions file410mo agoMITA579Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,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