Borrowing it
Nothing to install: this file belongs to martinnaithani/Fireteam. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/martinnaithani/Fireteam/main/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/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.
<a href="https://agentmods.dev/instructions/martinnaithani/fireteam/agents-md"><img src="https://agentmods.dev/badge/instructions/martinnaithani/fireteam/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01156 | $0.01156 |
| Opus 5.5 | $0.00462 | $0.00462 |
| Sonnet 5.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 2mo 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.
- 2mo 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 7mo ago), licensed MIT. It adds 1,156 tokens to every session, about $0.0046 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-08-31.
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).
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.
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).
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 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).
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.