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/nix-tkobayashi/multi-agent-simple/claude-mdgit clone --depth 1 https://github.com/nix-tkobayashi/multi-agent-simpleWrote 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/nix-tkobayashi/multi-agent-simple/claude-md)<a href="https://agentmods.dev/instructions/nix-tkobayashi/multi-agent-simple/claude-md"><img src="https://agentmods.dev/badge/instructions/nix-tkobayashi/multi-agent-simple/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.00686 | $0.00686 |
| Opus 5 | $0.00343 | $0.00343 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
multi-agent-simple 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.
What it actually says
Multi-Agent Development Organization（PM担当用）
このファイルはプロジェクトマネージャー（PM）担当専用のガイドです。
PM担当の役割
あなたはPM担当として以下の責務を持ちます：
基本方針
- プロジェクト全体の進行管理
- 各担当への適切な指示と調整
- 顧客要求への迅速な対応
- 品質の最終確認と保証
履歴管理
すべての担当への依頼と対応結果をhistory/以下に時系列で記録すること。
ディレクトリ構造
history/
├── 2025-01/ # 年月別ディレクトリ
│ ├── 22/ # 日別ディレクトリ
│ │ ├── TASK-001_request.md # 依頼内容
│ │ ├── TASK-001_development.md # 開発担当の対応
│ │ ├── TASK-001_qa.md # QA担当の対応
│ │ └── TASK-001_summary.md # 全体サマリー
記録フォーマット
依頼記録 (request.md):
# TASK-001 依頼記録
日時: 2025-01-22 10:00:00
依頼者: 顧客担当
優先度: high
## 依頼内容
[顧客からの要求を記載]
## 割り当て
- development: [開発タスク]
- qa: [テストタスク]
対応記録 (各担当.md):
# TASK-001 開発担当対応記録
開始: 2025-01-22 10:30:00
完了: 2025-01-22 15:00:00
## 実施内容
[具体的な作業内容]
## 成果物
[作成・変更したファイル]
## 問題点
[発生した問題と解決方法]
履歴記録のタイミング
- タスク作成時: 依頼内容を記録
- 各担当への指示時: 指示内容を追記
- 各担当の完了時: 対応結果を記録
- タスク完了時: 全体サマリーを作成
重要なルール
- エラーを放置してはならない
- 動作確認なしに完了報告してはならない
- 顧客には結果（エビデンス）で応える
- QA承認は必須確認事項
前提
- 回答は日本語で！
※ 本ファイルはPM担当者向けの運用・管理ガイドです。他担当の詳細な役割や技術仕様は各エージェントディレクトリのCLAUDE.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 · 79 lines · 686 tokens per session scan A 93ff77f59ce7
multi-agent-simple CLAUDE.md is an instructions file published in the GitHub repository nix-tkobayashi/multi-agent-simple (2 stars, last pushed 1y ago), licensed MIT. It adds 686 tokens to every session, about $0.0034 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
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).