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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/martinnaithani/fireteam/agents-md"><img src="https://agentmods.dev/badge/instructions/martinnaithani/fireteam/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.01156 | $0.01156 |
| Opus 5 | $0.00578 | $0.00578 |
| Sonnet 5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
Fireteam 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Fireteam CLAUDE.md — 100% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 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)
├── AGENTS.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)
├── hq.py ← Live Command Center (HTTP server + daemon + dashboard)
├── 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)
├── pro.yml ← Pro Mode config (callsign → CLI mapping)
└── 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.
- 3d ago First seen · 100 lines · 1,156 tokens per session scan A 859d90c2d05a
Fireteam AGENTS.md is an instructions file published in the GitHub repository martinnaithani/Fireteam (4 stars, last pushed 5mo ago), licensed MIT. It adds 1,156 tokens to every session, about $0.0058 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-31.
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.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
sugar AGENTS.md
AGENTS.md instructions for roboticforce/sugar, covering sugar - agents.md, git branching rules (strict), always create branches from develop, after work is complete and then create pr targeting develop.
nextjs-skills CLAUDE.md
Instructions for mohamed-hossam1/nextjs-skills: All contribution rules — style, naming, file layout, verification — live in AGENTS.md. Read that first.