Shogun Agent StatusSAFE
Samurai-inspired multi-agent system for Claude Code. Orchestrate parallel AI tasks via tmux with shogun → karo → ashigaru hierarchy.
Overview
Samurai-inspired multi-agent system for Claude Code. Orchestrate parallel AI tasks via tmux with shogun → karo → ashigaru hierarchy.
cf15f16c9e1cOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| codex | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: shogun-agent-status
description: 全エージェント(家老・足軽1-7・軍師)の稼働状態を一覧表示するスキル。tmux pane状態(稼働中/待機中/不在)とタスクYAML状態(task_id, status)と未読inbox数を統合表示。「稼働確認」「エージェント状態」「布陣確認」「agent status」で起動。
---
# /agent-status - エージェント稼働確認
## Overview
全エージェントの稼働状態を2つのデータソースから統合判定して一覧表示する。
1. **Pane状態**: tmux capture-paneの末尾5行からCLI固有のidle/busyパターンを検出
2. **タスクYAML**: `queue/tasks/{agent}.yaml` のtask_idとstatus
3. **未読inbox**: `queue/inbox/{agent}.yaml` の未処理メッセージ数
Claude Code / Codex CLI 両方に対応。
## When to Use
- 「稼働確認」「エージェント状態」「布陣確認」と言われた時
- 足軽が暇そうか確認したい時
- タスク配分前に空いているエージェントを探す時
- 誰かが止まっているか調べたい時
## Instructions
以下のコマンドを実行する:
```bash
bash scripts/agent_status.sh
```
## 出力の読み方
| Column | 意味 |
|--------|------|
| Agent | エージェント名 |
| CLI | CLI種別(claude/codex) |
| Pane | tmux pane状態: 稼働中/待機中/不在 |
| Task ID | タスクYAMLのtask_id(---=未割当) |
| Status | タスクYAMLのstatus: assigned/done/idle等 |
| Inbox | 未読inboxメッセージ数 |
## 状態の解釈
- **Pane=待機中 + Status=done**: 完了済み、次タスク待ち。新タスク配分可能。
- **Pane=稼働中 + Status=assigned**: 正常にタスク実行中。放置してよい。
- **Pane=待機中 + Status=assigned**: タスク割当済みだがCLIが止まっている。要調査。
- **Pane=稼働中 + Status=done**: タスク完了後に別作業中(inbox処理等)。
- **Inbox > 0**: 未読メッセージあり。エージェントが処理していない可能性。
- **Pane=不在**: tmux paneが存在しない(shutsujin未実行 or pane killed)。Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
cf15f16c9e1cfull audit observations/trust-audit/skill/yohey-w__shogun-agent-status.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | cf15f16c9e1c | SAFE | B | 89 | first audit |
Questions
What does the Shogun Agent Status skill do?
Samurai-inspired multi-agent system for Claude Code. Orchestrate parallel AI tasks via tmux with shogun → karo → ashigaru hierarchy.
Is Shogun Agent Status safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Shogun Agent Status access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Shogun Agent Status work with?
Its documentation mentions claude-code and codex. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (cf15f16c9e1c), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.