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/agentculture/fleet-cli/claude-mdgit clone --depth 1 https://github.com/agentculture/fleet-cliWhat 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.03893 | $0.03893 |
| Opus 5 | $0.01946 | $0.01946 |
| Sonnet 5 | $0.00779 | $0.00779 |
| Haiku 4.5 | $0.00389 | $0.00389 |
Grade A, and why
fleet-cli 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 yesterday.
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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repo actually is
fleet-cli is an AgentCulture mesh agent, scaffolded from the
culture-agent-template. Two things are true at once, and you must hold both:
- Stated domain (the goal): "Agent and CLI to control a fleet of drones
(multiple UAVs), built on
drone-cli— coordinate, command, and monitor many drones at once." This is the agent's identity and the direction of future work. - Actual code today (the reality): a generic agent-first CLI scaffold —
identity/introspection verbs (
whoami,learn,explain,overview,doctor,cli) plus the vendored AgentCulture skill kit. No drone / UAV /drone-clifunctionality exists yet. The CLI's own self-description still reads "a clonable template for AgentCulture mesh agents" (seelearn.py,explain/catalog.py,README.md).
When you add the drone-fleet functionality, you are specializing the scaffold:
add new noun groups under fleet/cli/_commands/, give them catalog entries, and
update the self-description strings — all while preserving the contracts below.
Do not invent drone behavior that isn't asked for, and don't assume any drone
plumbing is present.
Commands
uv sync # install deps into .venv (uses uv.lock)
# Run the CLI — the console script is `fleet`, NOT `fleet-cli` (see gotcha below)
uv run fleet whoami
uv run python -m fleet whoami # equivalent
uv run fleet learn --json # every verb supports --json
# Tests
uv run pytest -n auto # full suite, parallel (xdist)
uv run pytest tests/test_cli.py::test_whoami_text # a single test
uv run pytest -n auto --cov=fleet --cov-report=term # with coverage (CI gate: fail_under=60)
# Lint / format (exactly what the CI `lint` job runs)
uv run black --check fleet tests # line length 100
uv run isort --check-only fleet tests # black profile
uv run flake8 fleet tests # max-line-length 100, ignores E203/W503
uv run bandit -c pyproject.toml -r fleet
markdownlint-cli2 "**/*.md" "#node_modules" "#.local" "#.claude/skills" "#.teken"
uv run teken cli doctor . --strict # the agent-first rubric gate (see below)
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.
- yesterday First seen · 266 lines · 3,893 tokens per session scan A e09770b80dbd
fleet-cli CLAUDE.md is an instructions file published in the GitHub repository agentculture/fleet-cli (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,893 tokens to every session, about $0.0195 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
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).
next.js 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, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.