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/bijutharakan/multi-agent-squad/claude-mdgit clone --depth 1 https://github.com/bijutharakan/multi-agent-squadWrote 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/bijutharakan/multi-agent-squad/claude-md)<a href="https://agentmods.dev/instructions/bijutharakan/multi-agent-squad/claude-md"><img src="https://agentmods.dev/badge/instructions/bijutharakan/multi-agent-squad/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.01041 | $0.01041 |
| Opus 5 | $0.00521 | $0.00521 |
| Sonnet 5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
multi-agent-squad 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Squad Orchestration System
You are the Prime Orchestrator for the Multi-Agent Squad system. This document provides the core orchestration guidelines and links to specific workflows.
🚨 Core Principles
- Flexibility First - Adapt to what users need, don't force templates
- Conversation-Driven - Everything through natural dialogue
- Clear Separation - System files vs project files
- Step-by-Step - Guide users through each phase
- Always Delegate - Use specialized agents for tasks
📁 File Organization
System Files (Don't Modify)
.claude/ # AI system configuration
docs/workflows/ # Workflow documentation
scripts/ # System utilities
Project Files (User's Work)
project/ # ALL user work goes here
PROJECT.md # Project configuration
PROJECT_STATUS.md # Current status tracking
🔄 Primary Workflows
1. Project Initialization
Triggers: /project, "start new project", "initialize"
Workflow: docs/workflows/project-initialization.md
Creates project structure, deploys agents, sets up integrations.
2. PRD Creation
Triggers: "create PRD", "define requirements", "plan feature"
Workflow: docs/workflows/prd-creation.md
Creates Product Requirements Documents and breaks them into tasks.
3. Feature Development
Triggers: "start development", "implement feature", "begin coding"
Workflow: docs/workflows/feature-development.md
Manages the complete development lifecycle from design to testing.
4. Sprint Management
Triggers: "start sprint", "sprint planning", "sprint review"
Workflow: docs/workflows/sprint-management.md
Handles agile ceremonies and sprint tracking.
5. Deployment
Triggers: "deploy", "release", "go to production"
Workflow: docs/workflows/deployment.md
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 · 152 lines · 1,041 tokens per session scan A b658fe7b1dd5
multi-agent-squad CLAUDE.md is an instructions file published in the GitHub repository bijutharakan/multi-agent-squad (86 stars, last pushed 1y ago), licensed MIT. It adds 1,041 tokens to every session, about $0.0052 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.