multi-agent-shogun is a system that coordinates multiple AI coding command-line agents through a hierarchy of managers, strategists, and workers. Developers use it to split coding requests into parallel tasks and monitor their execution through tmux.
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 skills add yohey-w/multi-agent-shogun --skill shogun-readme-syncgit clone --depth 1 https://github.com/yohey-w/multi-agent-shogunWrote 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/skills/yohey-w/multi-agent-shogun/shogun-readme-sync)<a href="https://agentmods.dev/skills/yohey-w/multi-agent-shogun/shogun-readme-sync"><img src="https://agentmods.dev/badge/skills/yohey-w/multi-agent-shogun/shogun-readme-sync/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yohey-w/multi-agent-shogun/shogun-readme-sync"><img src="https://agentmods.dev/badge/skills/yohey-w/multi-agent-shogun/shogun-readme-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01139 |
| Opus 5 | $0.00033 | $0.00570 |
| Sonnet 5 | $0.00013 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
shogun-readme-sync 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shogun-readme-sync - README日英同期
Overview
README.md（英語）とREADME_ja.md（日本語）の差分を検出し、不足セクションの追加・番号ズレの修正を行う。
README変更時のワークフロー:
- 差分検出（どちらが新しいか自動判定）
- 不足セクションのリストアップ
- 翻訳・追記の実行
- セクション番号の整合性チェック
When to Use
- READMEを編集した後（機能追加、セクション追加、構成変更）
- 「README更新」「README同期」「readme sync」と言われた時
- 新機能をREADMEに書いた後に「日本語版も」と言われた時
- PR作成前のREADME整合性チェック
Instructions
Step 1: 差分検出
両ファイルを読み込み、以下の観点で差分を検出する:
# 両ファイルを読む
Read README.md
Read README_ja.md
チェック項目:
| 項目 | 確認方法 |
|---|---|
| セクション数 | ### ヘッダーの数が一致するか |
| セクション番号 | 番号付きセクション（### ... 1., ### ... 2.等）の連番が正しいか |
| ファイル構成 | File Structure / ファイル構成セクション内のファイル一覧が一致するか |
| バージョンセクション | What's New / 新機能 セクションが両方に存在するか |
| 折りたたみ内容 | <details> ブロックの有無が一致するか |
Step 2: 差分レポート
検出した差分を報告する:
README同期チェック結果:
EN → JA で不足:
- セクション「Agent Status Check」が日本語版にない
- ファイル構成に lib/agent_status.sh が未掲載
- v3.3.2セクションがない
JA → EN で不足:
- （なし）
セクション番号ズレ:
- JA: スクリーンショットが5番だがENでは6番
Step 3: 同期実行
差分を修正する。翻訳のルール:
| EN | JA |
|---|---|
| Agent Status Check | エージェント稼働確認 |
| Screenshot Integration | スクリーンショット連携 |
| Context Management | コンテキスト管理 |
| Phone Notifications | スマホ通知 |
| Pane Border Task Display | ペインボーダータスク表示 |
| Shout Mode | シャウトモード（戦国エコー） |
| Event-Driven Communication | イベント駆動通信 |
| Parallel Execution | 並列実行 |
| Non-Blocking Workflow | ノンブロッキングワークフロー |
| Cross-Session Memory | セッション間記憶 |
| Bottom-Up Skill Discovery | ボトムアップスキル発見 |
翻訳方針:
- 技術用語はそのまま（tmux, YAML, CLI, MCP, inotifywait等）
- コードブロック内のコマンドは翻訳しない
- 出力例は日本語版に合わせる（「稼働中」「待機中」等）
- 絵文字はENと同じものを使う
Step 4: 整合性最終チェック
修正後、以下を確認:
- 両ファイルのセクション数が一致
- 番号付きセクションの連番が正しい
- ファイル構成セクションのエントリが一致
- バージョンセクションが両方に存在
Guidelines
- ENが正: 新機能は基本的にENに先に書かれる。JA側を追従させる
- JA独自表現は維持: 日本語版の「戦国エコー」等の独自表現はそのまま残す
- 一方通行にしない: ENにしかない変更もJAにしかない変更も両方検出する
- セクション番号は自動繰り上げ: 中間にセクションを挿入した場合、後続の番号を全て繰り上げる
- コードブロック内は触らない: bash/yaml/markdownのコードブロック内テキストは翻訳対象外
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.
- 10d ago First seen · 105 lines · 66 tokens per session scan A 3012ad9e4784
shogun-readme-sync is a skill published in the GitHub repository yohey-w/multi-agent-shogun (1,420 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,139 once invoked, about $0.0003 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 skills, from other repositories
translate
Translate text between Russian and English (or other languages on request), preserving register, tone, and meaning rather than producing a literal word-for-word rendering. Use when the user wants a passage translated. Trigger when the user says "translate", "translate this to Russian/English", or pastes Russian text…
skill-agent-mapping
This skill should be used when looking up which agents own or consume specific skills, understanding skill-agent relationships, or routing tasks based on skill ownership.
exploration-strategy
This skill should be used when exploring codebases, finding patterns, searching for code, gathering context, or understanding code structure before planning or implementation.
team-decision
This skill should be used when deciding whether to use Agent Teams for parallel execution or sequential subagent orchestration, based on task analysis, independence criteria, and cost-benefit.
agentsview-usage
Search prior session history to recall how similar work was handled before. Use when you want to leverage a past approach, check prior experience on a topic, answer "how was this handled before", or cross-verify current handling against precedent from earlier sessions.
graphify-usage
This skill should be used when querying the graphify knowledge graph for structural codebase information, choosing between graph tools and grep, or interpreting graph query results.