Borrowing it
Nothing to install: this file belongs to anurmatov/phleet. 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/anurmatov/phleet/main/CLAUDE.mdgit clone --depth 1 https://github.com/anurmatov/phleetWrote 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/anurmatov/phleet/claude-md)<a href="https://agentmods.dev/instructions/anurmatov/phleet/claude-md"><img src="https://agentmods.dev/badge/instructions/anurmatov/phleet/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.02428 | $0.02428 |
| Opus 5 | $0.01214 | $0.01214 |
| Sonnet 5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade C, and why
phleet CLAUDE.md scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
dir is gitignored — `rm -rf fleet/` to reset. How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet — Autonomous AI Agent System
Repository Structure
src/
├── Fleet.Agent/ — core agent process (Telegram bot + multi-provider executor)
├── Fleet.Orchestrator/ — agent registry, Temporal workflow polling, MCP + REST + WebSocket
├── Fleet.Temporal/ — workflow orchestration bridge (MCP server)
├── Fleet.Bridge/ — RabbitMQ relay for inter-agent messaging
├── Fleet.Memory/ — semantic memory MCP server (Qdrant + embeddings)
├── Fleet.Shared/ — shared utilities
└── fleet-dashboard/ — React SPA for agent monitoring and lifecycle management
Dockerfile — agent image (multi-stage)
Dockerfile.temporal — temporal bridge image
entrypoint.sh — container init script
gh-auth.sh — GitHub App JWT generation utility
seed.example.json — example agent bootstrap config (setup.sh copies → ./fleet/seed.json)
docker-compose.example.yml — full stack example (setup.sh copies → ./fleet/docker-compose.yml)
.env.example — required environment variables (setup.sh copies → ./fleet/.env)
setup.sh — guided installer
upgrade.sh — rebuild images + restart (no prompts)
./fleet/ — gitignored runtime data dir (created by setup.sh)
Build Commands
# Build the entire solution
dotnet build
# Build a specific project
dotnet build src/Fleet.Agent/Fleet.Agent.csproj
# Run tests
dotnet test
# Build Docker images (from repo root)
docker build -t fleet:agent .
docker build -t fleet:memory -f src/Fleet.Memory/Dockerfile .
docker build -t fleet:orchestrator -f src/Fleet.Orchestrator/Dockerfile .
docker build -t fleet:temporal-bridge -f Dockerfile.temporal .
docker build -t fleet:bridge -f src/Fleet.Bridge/Dockerfile .
docker build -t fleet:dashboard \
--build-arg VITE_AUTH_TOKEN=your-token \
-f src/fleet-dashboard/Dockerfile .
# Dashboard (React)
cd src/fleet-dashboard
npm install
npm run dev # local dev server
npm run build # production build
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.
- today Changed fc27af413291
- 4d ago Changed · +25 lines · +432 tokens per session 84441f45dd40
- 8d ago First seen · 162 lines · 1,996 tokens per session scan C 05b2ffbef78a
phleet CLAUDE.md is an instructions file published in the GitHub repository anurmatov/phleet (18 stars, last pushed today), licensed MIT. It adds 2,428 tokens to every session, about $0.0121 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
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
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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 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).