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/ethanhq/cc-fleet/claude-mdgit clone --depth 1 https://github.com/ethanhq/cc-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/ethanhq/cc-fleet/claude-md)<a href="https://agentmods.dev/instructions/ethanhq/cc-fleet/claude-md"><img src="https://agentmods.dev/badge/instructions/ethanhq/cc-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 | $0.02549 | $0.02549 |
| Opus 5 | $0.01274 | $0.01274 |
| Sonnet 5 | $0.00510 | $0.00510 |
| Haiku 4.5 | $0.00255 | $0.00255 |
Grade A, and why
cc-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 5d 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 — 159 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 is
cc-fleet is a Go CLI (+ a Claude Code plugin) that runs third-party LLM providers
(DeepSeek, GLM, Kimi, Qwen, MiniMax — anything with an Anthropic-compatible API, plus
ChatGPT-subscription codex and OpenAI-protocol endpoints) as real Claude Code workers.
The core trick: a provider worker is a genuine claude process whose LLM backend is swapped
by launching it with --settings <provider-profile>.json (which sets ANTHROPIC_BASE_URL +
an apiKeyHelper) and --model <provider-model-id>. The main session's own auth (OAuth or
API key) is never touched.
There are four execution lanes — internalize this split, most of the code maps onto it:
- Teammate —
internal/spawn. A long-lived providerclaudein a tmux pane; the user's main session drives it via nativeTeamCreate/SendMessage. Stateful, reusable. Unix-only. - Subagent —
internal/subagent.claude -pheadless, one-shot (or--backgroundwith a job file); classifiedResultenvelope on stdout. The reserved idclauderuns the leaf on the user's own Claude login (explicit-only; subagent/workflow lanes only — no profile, no keyget). - Workflow —
internal/workflow. A detached engine running a JS script on an embedded goja VM; eachagent()leaf is a provider subagent. Journaled (--resume), leaves can be held/restarted live,workflow waitis the push-notification verb. - Interactive —
internal/run. Execs a provider-backed interactiveclaudein the current terminal. No tmux, no team, no locks.
The skills (skills/{subagent,team,workflow}/SKILL.md) teach the main Claude session when
to pick each lane. They are not loaded when you work on this repo — product, not project
config.
The full system design — fingerprint recipe, key safety, provider classes/daemon, workflow
engine, lock map, platform matrix — is docs/architecture.md.
Read it before structural changes; this file keeps only what an editing agent needs constantly.
The user-facing references are docs/cli.md (zh mirror docs/cli.zh.md) and
docs/workflows.md — update them when you change a command, flag,
envelope, or the workflow script API.
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.
- 5d ago First seen · 159 lines · 2,549 tokens per session scan A 4751bb17b21e
cc-fleet CLAUDE.md is an instructions file published in the GitHub repository ethanhq/cc-fleet (210 stars, last pushed 16d ago), licensed Apache-2.0. It adds 2,549 tokens to every session, about $0.0127 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-30.
Other instructions, from other repositories
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
ai-agents push-lock.instructions.md
Instructions for rjmurillo/ai-agents, covering one push lock path, must, must not, historical measurements and commit guard.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
ai-agents security.instructions.md
Instructions for rjmurillo/ai-agents, covering security file rules, must, should, must not and references.
oastools GEMINI.md
Instructions for erraggy/oastools, covering gemini.md, project overview, building and running, key commands and development conventions.