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 karaage0703/ai-assistant-workspace --skill xs-multi-agentgit clone --depth 1 https://github.com/karaage0703/ai-assistant-workspaceWrote 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/karaage0703/ai-assistant-workspace/xs-multi-agent)<a href="https://agentmods.dev/skills/karaage0703/ai-assistant-workspace/xs-multi-agent"><img src="https://agentmods.dev/badge/skills/karaage0703/ai-assistant-workspace/xs-multi-agent/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/karaage0703/ai-assistant-workspace/xs-multi-agent"><img src="https://agentmods.dev/badge/skills/karaage0703/ai-assistant-workspace/xs-multi-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 19 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Rogue Agent · line 193 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 202 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00095 | $0.03454 |
| Opus 5 | $0.00048 | $0.01727 |
| Sonnet 5 | $0.00019 | $0.00691 |
| Haiku 4.5 | $0.00010 | $0.00345 |
Grade A, and why
xs-multi-agent 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 11d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
マルチエージェント協調スキル
異なるAI providerから独立意見を得て、共通論点で考えた結果を統合する。 同じproviderの子エージェントを増やすだけの並列処理とは区別する。
重要: このスキルは毎回、最初に利用可能エージェントを検出する。CLIの入れ替わり、ログイン状態、クォータ、環境差を固定表で決め打ちしない。
最初に必ずやること
bash [SKILL_DIR]/scripts/check_agents.sh
このコマンドは、各エージェントに軽いプロンプトを投げ、skills/xs-multi-agent/SKILL.md を読めるかまで確認する。成功判定には固定トークン CHECK_AGENTS_OK を使い、解釈差のある自然言語回答を判定に使わない。各サービスのクォータを少量使う。
軽量にコマンド存在とバージョンだけ見たい時:
bash [SKILL_DIR]/scripts/check_agents.sh --no-smoke
このコマンドは $STATE_DIR/multi-agent/agents.json を作成・更新し、生成したパスを出力する。
STATE_DIR は STATE_DIR="${STATE_DIR:-${WORKSPACE_PATH:-$HOME}/.xangi}" として扱う。WORKSPACE_PATH が未設定なら $HOME/.xangi/multi-agent/agents.json に保存される。設定ファイルはランタイム状態なので git 管理しない。
設定ファイルの見方
available: true: コマンドがPATH上にあり、最低限のバージョン取得に成功ready: true: smoke 実行時に短い依頼が成功ready: false: smoke 実行時にログイン切れ、usage limit、実行失敗を検出ready: null:--no-smoke実行時など、実依頼の疎通は未確認recommended: true: 通常の依頼先候補provider_family: OpenAI / Anthropic / xAI / Google等の独立性を判定する単位- 複数providerのモデルを選べるCLIは、実providerを証明できるまで
unknownとしてpanel票に数えない scope: current_turn: 現在のセッション内だけ有効volatile: true: セッション、チャンネル、モデル、プロンプトで実体が変わるready_agents: 動作確認に成功した外部エージェントusable_agents:ready=trueかつrecommended=trueの標準外部依頼先
利用可能なエージェント
固定表ではなく、scripts/check_agents.sh の検出結果を使う。現在の検出対象:
| ID | 位置づけ | 標準扱い |
|---|---|---|
self |
現在のAIセッション。調整役・統合役 | 候補配列には入れない |
codex |
設計判断、デバッグ、深い推論、コードレビュー | 推奨 |
claude |
広い推論、文章化、レビュー | 推奨（クォータ注意） |
grok |
別視点の設計・レビュー、実装案 | 推奨 |
cursor |
codebase Q&A、plan/ask modeレビュー | 推奨 |
antigravity |
Antigravity CLI | 推奨（smoke pass時のみ） |
追加・削除が必要になったら、scripts/check_agents.sh と scripts/run_agent.sh の両方を更新する。
ワークフロー
0. エージェント検出・設定更新
bash [SKILL_DIR]/scripts/check_agents.shを実行- 出力された
agents.jsonを読む usable_agentsを外部依頼先の基本候補にするready=falseはそのターンでは使わないselfは現在ターンの調整役として扱い、外部依頼先リストには混ぜないready=trueは短いsmoke成功だけを意味する。今回必要なネットワーク、workspace読取、filesystem watchまでは保証しない
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 228 lines · 95 tokens per session scan A a3d1a2fd936e
xs-multi-agent is a skill published in the GitHub repository karaage0703/ai-assistant-workspace (137 stars, last pushed 23d ago), licensed MIT. It adds 95 tokens to every session and 3,454 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…