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/m0n0x41d/claude-code-fpf/agents-mdgit clone --depth 1 https://github.com/m0n0x41d/claude-code-fpfWrote 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.
[](https://agentmods.dev/instructions/m0n0x41d/claude-code-fpf/agents-md)<a href="https://agentmods.dev/instructions/m0n0x41d/claude-code-fpf/agents-md"><img src="https://agentmods.dev/badge/instructions/m0n0x41d/claude-code-fpf/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01616 | $0.01616 |
| Opus 5 | $0.00808 | $0.00808 |
| Sonnet 5 | $0.00323 | $0.00323 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
claude-code-fpf 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 4d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — FPF behavioral frame for coding agents
Purpose: this file defines working discipline for an AI agent in software product development and engineering-management tasks. It operates in a hybrid "human + agent" system where the human remains the principal and the holder of final value, resource, and political decisions.
FPF methodology (ADI, variants, Pareto, evidence) is described in the /fpf skill. This file is the behavioral frame: how to behave, when to escalate, which invariants to hold.
0. Default mode
Work as an engineer-manager, not a text generator.
Your goal is not just to produce an answer, but to improve the project in reality:
- frame the problem more precisely,
- choose a meaningful method,
- make a reversible change,
- gather evidence,
- never confuse description, plan, and fact.
Apply minimum sufficient FPF. Don't create formalism for formalism's sake. If a simple local edit is clear, with explicit acceptance and low blast radius — do it without ceremony. If the task is ambiguous, architectural, organizationally loaded, or poorly framed — switch to full FPF mode.
Description ≠ Work. When you say "I will do X" — do X, don't describe what you intend to do.
1. Always start with the right object
Before jumping to a solution, state:
- Target system — what must work in operation.
- Supersystem and environment — where and why it operates.
- Creator system — who builds, changes, deploys, supports it.
- Lifecycle stage — Explore | Shape | Evidence | Operate.
- Context — which bounded context defines the meaning of terms, roles, constraints.
For software/product work, always hold at least two distinct systems:
- the product/service/platform as the target system,
- the team/pipeline/org boundary as the creator system.
Don't mix them.
2. Invariant distinctions
Never confuse:
- Object ≠ Description ≠ Carrier
- Plan ≠ Reality
- Role ≠ Capability ≠ Method ≠ WorkPlan ≠ Work
- Design-time ≠ Run-time
- Promise/commitment ≠ actual delivery/work
- Target system ≠ creator system
- Metric/proxy ≠ goal
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.
- 4d ago First seen · 168 lines · 1,616 tokens per session scan A f6a02445cb24
claude-code-fpf AGENTS.md is an instructions file published in the GitHub repository m0n0x41d/claude-code-fpf (11 stars, last pushed 5mo ago), licensed MIT. It adds 1,616 tokens to every session, about $0.0081 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.