Borrowing it
Nothing to install: this file belongs to chankov/agent-fleet. 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/chankov/agent-fleet/main/CLAUDE.mdgit clone --depth 1 https://github.com/chankov/agent-fleetWrote 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/chankov/agent-fleet/claude-md)<a href="https://agentmods.dev/instructions/chankov/agent-fleet/claude-md"><img src="https://agentmods.dev/badge/instructions/chankov/agent-fleet/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.1 | $0.02462 | $0.02462 |
| Opus 5 | $0.01231 | $0.01231 |
| Sonnet 5 | $0.00492 | $0.00492 |
| Haiku 4.5 | $0.00246 | $0.00246 |
Grade A, and why
agent-fleet 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-fleet
This is the Agent Fleet project — a Pi-centered multi-agent orchestration system (agent-hub dispatcher, herdr fleet control plane, coms peer messaging, Hermes remote control) plus a library of production-grade engineering skills for AI coding agents. Lifecycle skills are partly vendored from upstream addyosmani/agent-skills — see docs/UPSTREAM-SKILLS.md.
Project Structure
bin/ → npm CLI: cli.js (agent-fleet entrypoint) + the deterministic installer engine in lib/ — manifest.js (catalogue), state.js (record + hashing), verify.js (evaluation), plan.js (decision), apply.js (the ONLY module that writes to a workspace), merge-forms.js (justfile region + settings.json keys); plus doctor/detect-agent/personas, build-manifest.js, snapshot-version.js, test/ (node --test)
install-manifest.json → GENERATED catalogue of every installable artifact — never hand-edit; run `node bin/build-manifest.js`
manifest-meta.json → the hand-edited half: groups, profiles, recommendations, consent classes, companion/requires/pinnedBy wiring, operator steps
skills/ → Agent Fleet-native + customized skills (SKILL.md per directory); shadows same-named vendored skills
vendor/agent-skills-upstream/ → Pristine upstream skill import at a pinned SHA — NEVER edit in place; policy + update procedure in docs/UPSTREAM-SKILLS.md
hermes/ → Hermes-facing skills (hub-conductor, hub-liaison) for remote conduction — see docs/coms-hermes-bridge.md
agents/ → 15 reusable agent personas, canonical pi frontmatter; installed as verbatim copies (no per-agent translation — pi is the only install target)
hooks/ → Session lifecycle hooks
scripts/ → Standalone scripts (team-up herdr launcher for reusable coms peers; peer-launch single-peer `just fleet peer` launcher; scripts/lib/ pure fleet modules under node --test)
scripts/workflows/ → Headless `just flow` graphs and their code-owned phase, envelope, gate, permission, quality, change-capture, trace, and scoped TypeScript runtime
justfile → Recipes to launch pi with each harness plus the single public `flow` entry point
.changeset/ → Pending changesets; rolled into CHANGELOG.md + version bump by `changeset version`
.versions/ → Per-version artifact snapshots used by the version-aware update flow (snapshot-version.js)
.github/workflows/release.yml → On merge to main: opens "Version Packages" PR or runs `changeset publish`
.pi/prompts/ → pi-native lifecycle prompt templates
.pi/extensions/ → always-on pi utility extensions, auto-discovered by pi (mcp-bridge, chrome-devtools-mcp, compact-and-continue, btw, agent-fleet-update-check, pi-voice-stt). pi-voice-stt is gated/optional — it binds its Alt+S hotkey only when an STT provider is configured, otherwise it is a no-op
.pi/harnesses/ → selectable pi session harnesses — NOT auto-discovered; loaded explicitly via the justfile or `pi -e` (`just fleet hub` loads Fleet Core before agent-hub; every native child gets damage-control-continue)
.pi/agents/ → pi YAML configs (teams, chains, peers, dispatch-policy) used by the orchestration harnesses; dispatch-policy.yaml routes dispatch_agent calls to same-name coms peers (e.g. the `runner: claude-code` reviewers) with native fallback
.pi/skills/ → pi-runtime skills (e.g. bowser browser automation)
.pi/damage-control-rules.yaml → rule set for the damage-control harness
references/ → Supplementary checklists (testing, performance, security, accessibility, observability); each installs as a companion of the skills that cite it
docs/ → ARCHITECTURE.md (runtime layers + module map), UPSTREAM-SKILLS.md (vendoring policy — update it when touching vendor/ or shadowed skills), MIGRATION-agent-fleet.md (major-release migration matrix), setup guides, agent-fleet-setup.md (per-project overrides + ownership), npm-install.md (deterministic lifecycle reference), claude-code-coms-bridge.md and coms-hermes-bridge.md (bridge references), plus pi-extensions.md and pi-specs/ for the pi extensions
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.
- 2d ago First seen · 79 lines · 2,462 tokens per session scan A 83d1848dec37
agent-fleet CLAUDE.md is an instructions file published in the GitHub repository chankov/agent-fleet (14 stars, last pushed today), licensed MIT. It adds 2,462 tokens to every session, about $0.0123 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-09-03.
Other instructions, from other repositories
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.
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).
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).
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.
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.