agentmods.dev

esp-fc: Instructions file for Codex

AGENTS.md

esp-fc AGENTS.md is an instructions file for Codex, OpenCode from rtlopez/esp-fc. It costs 1,072 tokens per session, scanned A, original, MIT.

Repository instructions for Esp-FC, a C++17 flight-controller firmware project that runs on boards such as ESP32 and RP2040. They describe the code layout, platform rules, and how to add tested features.

In plain words
What is it for?
Use them when modifying firmware, device drivers, platform abstractions, or unit tests in this repository.
Why use it?
They give a coding agent the project rules before it changes embedded code. This helps avoid unsupported libraries, misplaced code, and untested changes.

Instructions file for CodexOpenCode

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

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

not rated 873repo +2 changed 28d ago A scan 1,072 tokens original MIT
View source ↗ rtlopez/esp-fc
Reuse

Borrowing it

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

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 esp-fc AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rtlopez/esp-fc/agents-md"><img src="https://agentmods.dev/badge/instructions/rtlopez/esp-fc/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,072 This file is loaded in full into every session.
When invoked 1,072 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.01072 $0.01072
Opus 5.5 $0.00429 $0.00429
Sonnet 5.5 $0.00214 $0.00214
Haiku 4.5 $0.00107 $0.00107

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

Security

Grade A, and why

esp-fc 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 28d 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 · 85 lines

How it starts

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

AGENTS.md

Guidelines for AI agents working on Esp-FC. Keep changes small, tested and portable.

Project overview

  • Flight controller firmware, C++17, PlatformIO.
  • Firmware targets: esp32, esp32s2, esp32s3, esp32c3, esp8266, rp2040, rp2350.
  • native env is host-only and used for unit tests.
  • Arduino dependency must be isolated in Hal namespace.
  • It is not allowed to include new Arduino libraries, as there is process of removing Arduino dependency.

Repository layout

  • src/main.cpp – thin entry point, all logic lives in libraries.
  • lib/Espfc/src/ – main firmware library:
    • Model.h, ModelConfig.h, ModelState.h – central state and persisted settings.
    • Control/, Sensor/, Input*, Output/, Rc/, Telemetry/, Blackbox/, Stream/ – feature modules.
    • Device/ – device drivers, Hal/ – platform abstraction, Target/ – board/target definitions.
    • Utils/ – filters, math, logger, storage, timing helpers.
  • lib/AHRS, lib/EscDriver, lib/Gps, lib/betaflight, ... – supporting libraries.
  • test/test_<area>/test_<area>.cpp – unit tests.
  • bin/ – helper scripts, docs/ – user and dev docs.

Before you start

  • Read the module you are about to change and its neighbours; follow the patterns already there.
  • Read docs/development.md for the contribution workflow.
  • Keep the diff minimal – no drive-by refactors, no unrelated formatting changes.

Implementing a feature

  1. Locate the right module; prefer extending existing abstractions over adding new layers.
  2. If the feature needs user settings, add them to ModelConfig.h (and defaults/reset paths) and wire them through Model.
  3. Keep platform-specific code in Hal/ or Target/; feature code stays portable.
  4. Wire up CLI / MSP / Blackbox / telemetry only when the feature actually needs it.
  5. Add or extend unit tests for the new behaviour.
  6. Run the verification commands below before declaring the work done.
  7. ESP8266 target is legacy; features may be excluded but must build.
  8. Do not modify code in betaflight library, it is updated manually.

Read the full file on GitHub · 85 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. 28d ago Changed · +4 lines · +65 tokens per session 050e0473c433
  2. 1mo ago Changed · +14 tokens per session 9f0533e7157f
  3. 1mo ago First seen · 81 lines · 993 tokens per session scan A 3a30ae8b8a58

Subscribe to this mod's changes

esp-fc AGENTS.md is an instructions file published in the GitHub repository rtlopez/esp-fc (873 stars, last pushed yesterday), licensed MIT. It adds 1,072 tokens to every session, about $0.0043 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-09-14.

Hardware and IoTTestingUnit testingdronedshotesp32flight-controllerhobbyrp2350
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