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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/nwiizo/ccswarm/agents-md"><img src="https://agentmods.dev/badge/instructions/nwiizo/ccswarm/agents-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.00474 | $0.00474 |
| Opus 5 | $0.00237 | $0.00237 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
ccswarm AGENTS.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 4d 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.
What it actually says
ccswarm Codex Guide
Goal
ccswarm is the workflow, governance, A2A, and provider execution layer.
Keep terminal/session primitives, provider output parsing, and persistence in
crates/ccswarm/src/session; keep workflow orchestration in
crates/ccswarm/src/workflow.
Read First
CLAUDE.mddocs/ARCHITECTURE.mddocs/APPLICATION_SPEC.md
Build And Verify
cargo fmt --allcargo clippy --workspace -- -D warningscargo test --workspacecargo run -p ccswarm -- --help
Project Rules
- Write comments, rustdoc, commit messages, and markdown docs in English.
- Prefer
Result<T, E>withthiserror; avoid.unwrap()in production code. - Prefer Rust-native patterns already used in this repo: type-state, channels, iterator pipelines, and actor-style isolation where they improve clarity.
- Keep workflow logic out of low-level
sessionhelpers. - Keep tests focused on core behavior instead of growing broad fragile suites.
- Never hardcode secrets. Use environment variables and
SensitiveStringwhen handling API keys.
Codex Assets
- Repo skills live in
.agents/skills/. - Custom subagents are defined in
.agents/agents/*.tomland registered from.codex/config.toml. - The original Claude configuration is mirrored under
.codex/claude/for reference. - Detailed project rules remain available in
.codex/claude/rules/*.md.
Available Subagents
frontend-specialistbackend-specialistdevops-specialistqa-specialistrust-fix-agentcode-refactor-agentarchitecture-reviewerall-reviewerreview-fix-agent
Recommended Codex Skills
review-fix: review the current diff, fix clear issues, then re-runcargo clippy --workspace -- -D warningsandcargo test --workspace --no-run. This is the repo-local Codex counterpart to the personalhome-self-reviewworkflow.
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.
- 4d ago First seen · 61 lines · 474 tokens per session scan A e05bca610ef7
ccswarm AGENTS.md is an instructions file published in the GitHub repository nwiizo/ccswarm (149 stars, last pushed 1mo ago), licensed MIT. It adds 474 tokens to every session, about $0.0024 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
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.
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.
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).
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.