agentmods.dev

flamingo-pcb: Instructions file for Codex

AGENTS.md

flamingo-pcb AGENTS.md is an instructions file for Codex, OpenCode from cheewee2000/flamingo-pcb. It costs 1,752 tokens per session, scanned A, a copy of flamingo-pcb CLAUDE.md, MIT.

Repository instructions for running Flamingo, a tool for designing circuit boards through an agent connection. They describe its local server, web interface, and available tool endpoint.

In plain words
What is it for?
Use them to run Flamingo locally, open its board interface, connect an agent, and configure server or routing timeouts.
Why use it?
They tell an agent how to start the server and connect to the board-design tools before attempting hardware work.

Instructions file for CodexOpenCode

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

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

not rated 10repo 4d ago A scan 1,752 tokens copy · 95% MIT
View source ↗ cheewee2000/flamingo-pcb
Reuse

Borrowing it

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

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 flamingo-pcb AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cheewee2000/flamingo-pcb/agents-md"><img src="https://agentmods.dev/badge/instructions/cheewee2000/flamingo-pcb/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,752 This file is loaded in full into every session.
When invoked 1,752 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 95% copy Near-identical to another mod 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.01752 $0.01752
Opus 5.5 $0.00701 $0.00701
Sonnet 5.5 $0.00350 $0.00350
Haiku 4.5 $0.00175 $0.00175

Measured 12d ago against content hash a0643964ceb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flamingo-pcb 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 12d 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.

Origin

This is a copy

95% identical to flamingo-pcb CLAUDE.md — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flamingo — notes for Codex

Flamingo is prompt-first PCB CAD you drive over MCP. This file is for a future Codex session working in this repo or using Flamingo to design a board. See README.md for the human-facing overview and docs/superpowers/specs/2026-07-16-flamingo-design.md for the full design spec.

Running the server

npm install && npm run build
node packages/server/dist/cli.js serve board.flamingo   # prints "Flamingo v0.1.0 serving …"
  • Serves the live UI at http://localhost:4242, streams board changes over /ws, and exposes the MCP endpoint at /mcp.
  • .mcp.json (repo root) wires the flamingo MCP server to /mcp — its 37 tools are available only while the server is running. Start the server first, then use the tools.
  • Port override: FLAMINGO_PORT. Autoroute timeout override: FLAMINGO_ROUTE_TIMEOUT_MS (default 300000).
  • Desktop app tabs: the Mac app opens each board in its own native tab, each with its own server + MCP endpoint (ports scanned up from 4242, kept stable per project across relaunches). On open it writes the board's MCP URL into the project folder's .mcp.json, so a Codex session started in that folder connects to that board automatically — separate sessions can drive separate boards concurrently.

Design workflow (tool names)

prompt → parts → place → connect → route → drc → export

  1. Choose parts. parts_search then parts_get. Always parts_get before wiring a part — it lists the real pad numbers you'll reference. datasheet_get downloads the part's datasheet PDF (global cache ~/.flamingo/datasheets/, plus a copy into the board's datasheets/ dir) — read it before stating any specs.
  2. Lay out. new_board (2/4/6 layers) → set_board_outline (rect with cornerRadius, polygon, or raw path) → place_component / move_component.
  3. Connect. connect_pins (net + REFDES.PAD refs) builds nets. create_net_class + assign_net_class set track width / clearance / via sizes per net.
  4. Board features. add_zone (copper pour), add_mounting_hole, add_silk_text, add_keepout. remove_item by id.
  5. Route. autoroute (Freerouting; passes, optional nets). unroute / get_ratsnest to iterate.
  6. Check. run_drc returns violations as data (never a tool error).
  7. Export. export_fab writes gerbers.zip + bom.csv + cpl.csv (+ board.render.svg) for JLCPCB.

Read the full file on GitHub · 127 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. 12d ago First seen · 127 lines · 1,752 tokens per session scan A a0643964ceb4

Subscribe to this mod's changes

flamingo-pcb AGENTS.md is an instructions file published in the GitHub repository cheewee2000/flamingo-pcb (10 stars, last pushed 4d ago), licensed MIT. It adds 1,752 tokens to every session, about $0.0070 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to flamingo-pcb CLAUDE.md, differing in 6 lines, and is treated as a copy.

Claude CodeHardware and IoTcadedafreeroutinggerberhardware-design
Related

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

microsoft/vscode · 9,715 tokens

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens