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/nwiizo/ccswarm/claude-mdgit clone --depth 1 https://github.com/nwiizo/ccswarmWrote 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/nwiizo/ccswarm/claude-md)<a href="https://agentmods.dev/instructions/nwiizo/ccswarm/claude-md"><img src="https://agentmods.dev/badge/instructions/nwiizo/ccswarm/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.01785 | $0.01785 |
| Opus 5 | $0.00892 | $0.00892 |
| Sonnet 5 | $0.00357 | $0.00357 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
ccswarm 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 6d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
What ccswarm does
Hire ccswarm when you have a coding task and want a PR-ready diff with quality gates already run, reproducibly. OK/NG-driven: you only press y or n.
- Provider-neutral workflow: Claude Code (default) and Codex execute code; GitHub Copilot CLI is probed only for migration diagnostics.
- Reproducible: declarative flow YAML → same quality every time.
- Traceable: NDJSON events + summaries in
.ccswarm/runs/<id>/.
Daily usage
ccswarm # interactive — ccswarm asks what to build
ccswarm pipeline --task "..." # single-shot: plan → implement → review
ccswarm queue add "..." # accumulate tasks during the day
ccswarm queue add --from-issue 42 # ingest a GitHub issue as a task
ccswarm queue drain # run all pending, y/n at commit+PR time
ccswarm auto --require-approval # unattended; pauses before commit until
# `ccswarm approve commit --id <run-id>`
ccswarm doctor # probe all providers (claude/codex/gh copilot)
After a run
ccswarm run list # recent runs
ccswarm tail # follow events of the current run, tail-like
ccswarm cost <run-id> # duration + token breakdown
ccswarm run view <run-id> # full event log
ccswarm run diff <a> <b> # compare two runs' timelines
ccswarm replay <run-id> # re-execute the recorded task
ccswarm undo <run-id> # advisory: show commits since run started
Authoring flows
ccswarm flow list # builtin + custom flows
ccswarm flow new <name> # scaffold a new flow (minimal|faceted)
ccswarm flow render <name> # preview composed prompts per stage
ccswarm flow check <name> # validate flow YAML
ccswarm flow eject <name> # copy builtin to .ccswarm/flows/
ccswarm facets [personas|policies|knowledge] # list facet library
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.
- 6d ago First seen · 163 lines · 1,785 tokens per session scan A 7f81086c5fab
ccswarm CLAUDE.md is an instructions file published in the GitHub repository nwiizo/ccswarm (149 stars, last pushed 1mo ago), licensed MIT. It adds 1,785 tokens to every session, about $0.0089 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
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).
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.
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).