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/martinnaithani/fireteam/claude-mdgit clone --depth 1 https://github.com/martinnaithani/FireteamWrote 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/martinnaithani/fireteam/claude-md)<a href="https://agentmods.dev/instructions/martinnaithani/fireteam/claude-md"><img src="https://agentmods.dev/badge/instructions/martinnaithani/fireteam/claude-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.01137 | $0.01137 |
| Opus 5 | $0.00568 | $0.00568 |
| Sonnet 5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
Fireteam CLAUDE.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 5d 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.
This is a copy
100% identical to Fireteam AGENTS.md — 5 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for Maintaining Fireteam
Read HISTORY.md first. It contains the full design evolution and WHY every decision was made.
What This Repo Is
Fireteam is a file-system-native protocol for coordinating AI agent squads. No server, no database, no dependencies — just markdown files. This is the boilerplate repo that users copy into their projects.
Critical Constraints
-
ZERO DEPENDENCIES. The
.fireteam/folder works with a text editor. The CLI needs only bash. The dashboard needs only Python 3.6+ stdlib. Do not add npm, pip, or any package manager. -
PORTABLE BASH. The CLI must work on macOS AND Linux. Use the
sedi()wrapper for sed. Do not usegrep -P(Perl regex),readlink -f(not on macOS), or GNU-specific flags. -
BACKWARD COMPATIBLE TEMPLATES. Thousands of projects may use these templates. Adding fields is safe. Renaming or removing fields breaks existing projects.
-
THE THREE PROMPTS ARE LOAD-BEARING.
START_MISSION.md,RESUME_AGENT.md, and the onboarding prompt each have a specific multi-step process. Every step exists for a reason documented in HISTORY.md. Do not simplify them without understanding the rationale.
File Structure
fireteam/
├── README.md ← GitHub landing page
├── HISTORY.md ← Design evolution (READ THIS)
├── CLAUDE.md ← You are here
├── PRD_TEMPLATE.md ← User fills this to start
├── START_MISSION.md ← Bootstrap prompt (creates Team Lead)
├── RESUME_AGENT.md ← Recovery prompt (after crashes)
├── fireteam.sh ← CLI tool (portable bash)
├── dashboard.html ← Visual status dashboard (open in Chrome/Edge)
├── LICENSE ← MIT
├── .gitignore
└── .fireteam/ ← THE PROTOCOL (users copy this into projects)
├── MISSION.md ← Why we're here
├── CONVENTIONS.md ← Rules of engagement
├── ROSTER.md ← Who's on the team
├── BOARD.md ← Objective status
├── INTEL.md ← Curated knowledge
├── README.md ← Quick reference
├── tasks/ ← OBJ-XXX.md files
├── handoffs/ ← HO-XXX.md files
├── comms/ ← THREAD-XXX.md files
├── decisions/ ← DEC-XXX.md files
├── memory/ ← YYYY-MM-DD.md field logs
├── checkpoints/ ← [callsign].md + soul + heartbeat files
├── presets/ ← Team configurations (Solo, Duo, Squad, Platoon)
└── templates/ ← 8 templates (task, handoff, thread, decision,
fieldlog, checkpoint, soul, heartbeat)
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.
- 5d ago First seen · 99 lines · 1,137 tokens per session scan A f3da0709b5a2
Fireteam CLAUDE.md is an instructions file published in the GitHub repository martinnaithani/Fireteam (4 stars, last pushed 5mo ago), licensed MIT. It adds 1,137 tokens to every session, about $0.0057 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Fireteam AGENTS.md, differing in 5 lines, and is treated as a copy.
Other instructions, from other repositories
pdca-agentic-coding-framework CLAUDE.md
Claude Code instructions for kenjudy/pdca-agentic-coding-framework, covering claude.md, what this repo is, commands, architecture and key files.
pdca-agentic-coding-framework AGENTS.md
AGENTS.md instructions for kenjudy/pdca-agentic-coding-framework, covering agent instructions, quick reference, landing the plane (session completion) and skill build system.
project-coding-companion-skill AGENTS.md
Instructions for rgranet/project-coding-companion-skill, covering project coding companion, author: ruben granet | version: 1.0.0 | license: mit, adapted from the claude skill of the same name, critical — read this first and high-level workflow.
humanfile copilot-instructions.md
Instructions for zhangyu94/humanfile, covering .human file boundaries, rules and behavior.
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.
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.