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/neftedollar/multiagent-template/claude-mdgit clone --depth 1 https://github.com/Neftedollar/multiagent-templateWrote 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/neftedollar/multiagent-template/claude-md)<a href="https://agentmods.dev/instructions/neftedollar/multiagent-template/claude-md"><img src="https://agentmods.dev/badge/instructions/neftedollar/multiagent-template/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.01295 | $0.01295 |
| Opus 5 | $0.00647 | $0.00647 |
| Sonnet 5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
multiagent-template 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{PROJECT_NAME}} — Business Workspace
{{PROJECT_DESCRIPTION}}
Founder: {{FOUNDER}}. Team: AI agents. Phase: {{PHASE}}.
How to start (required for every session)
1. Determine mode
| If the CEO... | Mode | What to do |
|---|---|---|
Called /orchestrator <task> |
CEO Mode | You = orchestrator. Read docs/process.md, then execute. |
Called /<role> <question> |
Single Expert | You = that role. Answer as expert, no pipeline. |
| Just asked a question | Chief of Staff | You = advisor. Help, suggest next step, recommend a role or /orchestrator. |
Launched via claude -p |
Autonomous | You = orchestrator. Read docs/process.md, pick tasks from backlog. |
2. Load context (depends on mode)
Always read:
- This file (already loaded)
If task involves code:
code/{{PROJECT_NAME}}/CLAUDE.md— architecture, build, tests
If you are orchestrator (CEO Mode / Autonomous):
docs/process.md— operational manual (pipelines, gates, escalation, retry). Source of truth.docs/role-capabilities.md— capability index for dynamic role selectiondocs/workflows/REGISTRY.md— workflow registry
If you need history/context:
docs/archive/— old processes and docs- O'Brien: use o-brien MCP recall tool (recent: 20)
3. Act
- Orchestrator: follow pipeline from
docs/process.md. Select roles viadocs/role-capabilities.md+ graph. Don't hardcode. - Single Expert: answer within your role. No pipeline.
- Chief of Staff: help CEO. Suggest
/orchestratorfor pipeline tasks. Suggest specific role for expert questions.
Workspace structure
~/{{PROJECT_NAME}}/
├── code/
│ └── {{PROJECT_NAME}}/ ← main code repo (has its own CLAUDE.md)
├── docs/
│ ├── process.md ← operational manual (source of truth for pipeline)
│ ├── role-capabilities.md ← capability index for role selection
│ ├── workflows/ ← workflow specs (REGISTRY.md + WORKFLOW-*.md)
│ ├── archive/ ← old processes and docs
│ └── ...
├── .claude/
│ └── commands/ ← slash commands (global roles + project-level ad-hoc roles)
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.
- 3d ago First seen · 121 lines · 1,295 tokens per session scan A a0bf9c5cafc9
multiagent-template CLAUDE.md is an instructions file published in the GitHub repository Neftedollar/multiagent-template (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,295 tokens to every session, about $0.0065 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-31.
Other instructions, from other repositories
COG-second-brain CLAUDE.md
Instructions for huytieu/COG-second-brain, covering cog second brain — framework instructions, verification harness (opt-in, off by default), visual verification (always apply, ui/ux tasks), delegation cap (always apply) and model routing — always apply.
agentic-playwright common-tasks.instructions.md
Instructions for idavidov13/agentic-playwright, covering ai prompt templates for agentic playwright, critical, instructions, phase 1: identify the task category and resolve paths and phase 2: select and customize the matching prompt template.
agentic-playwright debugging.instructions.md
Instructions for idavidov13/agentic-playwright, covering debugging, critical, capture defaults (this scaffold), built-in npm scripts for debugging and instructions.
agentic-playwright ai-native-workflow.instructions.md
Instructions for idavidov13/agentic-playwright, covering ai-native workflow, critical, main workflow (8 phases), phase 4 — confidence-gate format (mandatory) and proposal.
agentic-playwright data-strategy.instructions.md
Instructions for idavidov13/agentic-playwright, covering data strategy, critical, file locations, instructions and phase 1: classify the value you need.
agentic-playwright config.instructions.md
Instructions for idavidov13/agentic-playwright, covering configuration, critical, file locations, instructions and phase 1: understand how env files are loaded.