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 skills add martinnaithani/Fireteam --skill skillgit 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/skills/martinnaithani/fireteam/skill)<a href="https://agentmods.dev/skills/martinnaithani/fireteam/skill"><img src="https://agentmods.dev/badge/skills/martinnaithani/fireteam/skill/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/skills/martinnaithani/fireteam/skill"><img src="https://agentmods.dev/badge/skills/martinnaithani/fireteam/skill.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.00145 | $0.03079 |
| Opus 5.5 | $0.00058 | $0.01232 |
| Sonnet 5.5 | $0.00029 | $0.00616 |
| Haiku 4.5 | $0.00015 | $0.00308 |
Grade A, and why
fireteam 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 1mo 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fireteam — Persistent Memory for AI Coding Sessions
Fireteam gives AI coding agents a memory that survives session restarts, context limits, and crashes. It uses a .fireteam/ folder of structured markdown files — mission context, task state, progress checkpoints, and handoff notes — that the agent reads at session start and writes during work.
Primary use case: One agent working across multiple sessions on the same project. .fireteam/ files carry context forward so the agent never starts from zero.
Secondary use case: 2-6 agents coordinating on the same codebase through shared .fireteam/ files — task claims, handoffs, and conflict prevention.
Core mechanic: Every AI agent can read and write files. Fireteam uses the file system as the persistent memory layer.
CRITICAL: Scope Boundaries
Fireteam operates ONLY within the current working directory. These rules are non-negotiable:
-
NEVER navigate to, read, scan, or reference files outside the current working directory. Not parent directories, not sibling directories, not the user's home folder, not other projects. The project boundary is the current working directory — period.
-
NEVER search the filesystem for other projects. If the current directory is empty and the user asked to set up a fireteam, set it up HERE. Do not go looking for code elsewhere.
-
All
.fireteam/files are created in the current working directory. Not in a discovered project, not in a parent directory. -
Recon scans ONLY the current working directory. If the directory is empty, recon finds nothing — that's correct. Proceed as greenfield.
-
If the current directory seems wrong (empty when user said "existing project"), ASK the user: "This directory appears empty. Would you like to set up a greenfield fireteam here, or should you navigate to your project first?" Do NOT go exploring.
When to Use This Skill
Session continuity (primary):
- User wants their agent to remember context across sessions
- User says "continue my fireteam" or "pick up where I left off"
- User says "set up a fireteam" for a new or existing project
- User wants to save progress: "write a checkpoint"
- User is resuming after a crash or context limit
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/templates/board.md 741 B
- assets/templates/checkpoint.md 803 B
- assets/templates/decision.md 484 B
- assets/templates/fieldlog.md 288 B
- assets/templates/handoff.md 662 B
- assets/templates/heartbeat.md 1.2 KB
- assets/templates/intel.md 804 B
- assets/templates/mission.md 566 B
- assets/templates/roster.md 631 B
- assets/templates/soul.md 1.4 KB
- assets/templates/task.md 1.1 KB
- assets/templates/thread.md 407 B
- references/conventions.md 6.4 KB
- references/presets.md 7.0 KB
- references/recon.md 6.3 KB
- references/recovery.md 2.2 KB
- scripts/setup.sh 995 B runs code
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.
- 1mo ago First seen · 243 lines · 145 tokens per session scan A e7649a703c91
fireteam is a skill published in the GitHub repository martinnaithani/Fireteam (4 stars, last pushed 7mo ago), licensed MIT. It adds 145 tokens to every session and 3,079 once invoked, about $0.0006 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 skills, from other repositories
project-butler
A project-memory workflow that keeps a code project’s rules, current structure, documents, logs, tasks, and handoff notes organized.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
context-engineering
A project documentation framework that records a project's goals, requirements, roadmap, and current state in separate files. It also keeps those documents within set size limits for an AI coding agent.
error-experience-library
An error knowledge base that stores recurring error patterns, their causes, and the fixes that worked. It can search past entries and track whether each suggested fix succeeded.
chronicle-skysight
Use when recent Linux desktop activity memory would help answer a question or when the user asks to inspect or control Chronicle or Skysight.
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.