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/andrzejchm/fdb/agents-mdgit clone --depth 1 https://github.com/andrzejchm/fdbWhat 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.01534 | $0.01534 |
| Opus 5 | $0.00767 | $0.00767 |
| Sonnet 5 | $0.00307 | $0.00307 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
fdb 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 2d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guide for AI coding agents working in this repository.
Project Overview
fdb (Flutter Debug Bridge) — a pure Dart CLI tool that lets AI agents interact
with running Flutter apps on physical devices and simulators. It launches Flutter apps
as detached processes, communicates via POSIX signals and the VM Service Protocol
over WebSocket, and stores all session state under a per-project .fdb/ directory
(PID file, VM service URI, logs, launcher script). The session directory defaults to
<CWD>/.fdb/ and is overridden by --project <path> on fdb launch.
- Language: Dart 3.x (SDK
>=3.0.0 <4.0.0) - Runtime: Dart VM (standalone — not a Flutter app)
- External dependencies:
package:args(CLI argument parsing),package:vm_service(VM Service Protocol),package:image(image decoding/encoding),package:pubspec_manager(pubspec parsing), plus the Dart SDK (dart:io,dart:async,dart:convert). - Architecture: layered.
lib/core/is interface-agnostic business logic;lib/cli/is the CLI adapter that wraps it. The split is enforced by directory convention so a future MCP server, REST API, or library consumer can call the same core functions without going through ArgParser or stdout tokens. - Entry point:
bin/fdb.dartdispatches to CLI adapter functions (runXxxCli) viaswitch. Adapters call intolib/core/commands/.
Directory layout
bin/fdb.dart # CLI entry point — command dispatcher
lib/
constants.dart # File paths + timeouts (used by both layers)
core/ # Interface-agnostic business logic
app_died_exception.dart # Domain exception
process_utils.dart # PID/process helpers
launch_failure_analyzer.dart
models/
command_result.dart # Marker base for sealed result hierarchies
commands/<name>/
<name>.dart × 28 # verb function + `export '<name>_models.dart';`
<name>_models.dart × 28 # <Name>Input typedef + sealed <Name>Result
src/controller/ # Internal controller process implementation
controller.dart # Controller entrypoint logic
controller_client.dart # CLI/core client for controller commands
commands/<name>.dart # Request + response + runner per controller command
vm_service/ # VM Service Protocol wrappers
cli/ # CLI adapter layer
args_helpers.dart # runCliAdapter, runSimpleCliAdapter, parseXY
adapters/
<name>_cli.dart × 28 # runXxxCli(args) — ArgParser + token formatting
packages/
fdb_helper/ # Flutter package — registers VM service extensions
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.
- 2d ago First seen · 121 lines · 1,534 tokens per session scan A 00400438aa85
fdb AGENTS.md is an instructions file published in the GitHub repository andrzejchm/fdb (45 stars, last pushed 4d ago), licensed MIT. It adds 1,534 tokens to every session, about $0.0077 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-30.
Other instructions, from other repositories
Amarok-Hider AGENTS.md
Instructions for deltazefiro/Amarok-Hider, covering amarok, project overview, build, e2e test and agent rules.
AppClaw CLAUDE.md
Instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
MobiAI-Core CLAUDE.md
Instructions for ArisGuimera/MobiAI-Core, covering mobiai — mobile development ai ecosystem, bootstrap and principles.
freetube CLAUDE.md
Instructions for leshkodev/freetube, covering claude.md, 1. what this project is, 2. non-negotiable constraints, 3. tech stack (locked) and 4. project structure.
ConsultMe CLAUDE.md
Instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.