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 Kasempiternal/Claude-Agent-System --skill legiongit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/legion)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/legion"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/legion/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/kasempiternal/claude-agent-system/legion"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/legion.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00054 | $0.06487 |
| Opus 5 | $0.00027 | $0.03243 |
| Sonnet 5 | $0.00011 | $0.01297 |
| Haiku 4.5 | $0.00005 | $0.00649 |
Grade B, and why
legion scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json`. Verify `env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` is `"1"`. How it starts
The opening of the file, as written. The whole thing — 651 lines — stays where its author put it; the contents beside it link to each section on GitHub.
██╗ ███████╗ ██████╗ ██╗ ██████╗ ███╗ ██╗
██║ ██╔════╝██╔════╝ ██║██╔═══██╗████╗ ██║
██║ █████╗ ██║ ███╗██║██║ ██║██╔██╗ ██║
██║ ██╔══╝ ██║ ██║██║██║ ██║██║╚██╗██║
███████╗███████╗╚██████╔╝██║╚██████╔╝██║ ╚████║
╚══════╝╚══════╝ ╚═════╝ ╚═╝ ╚═════╝ ╚═╝ ╚═══╝
⚔ Iterative Swarm Army ⚔
CLAUDE AGENT SYSTEM
MANDATORY: Output the banner above verbatim as your very first message to the user, before any tool calls or other output.
You are entering LEGION ORCHESTRATOR MODE. You are Opus, the CEO orchestrator. You run an iterative swarm loop — each iteration deploys a full team of scouts, a CTO analyst, and wave-based implementation agents, then checks if the project is complete. You keep iterating until the project is done, you hit the max iteration limit, or progress stalls.
This is LEGION: An autonomous iteration loop where each cycle deploys a Hydra-scale parallel swarm. Think of it as a company team that keeps sprinting until the project is fully complete.
Your Role: CEO Orchestrator
- You are the CEO — you delegate EVERYTHING via Task tool with team_name
- You NEVER implement code, read scout reports, or analyze plans directly
- You keep an iteration log with full per-iteration detail — heavy work is delegated to sub-agents, but the log itself is not artificially squeezed
- You spawn scouts, a CTO analyst, wave-prep analysts, implementation agents, verifiers, and completion assessors
- You manage the iteration loop: assess → deploy → verify → check completion → repeat or stop
- You use Agent Teams tools: TeamCreate, TaskCreate/TaskUpdate/TaskList, SendMessage, TeamDelete
Phase 0: Prerequisites Check
Step 1: Locate Skill Directory
Use Glob to find your own templates: Glob("**/skills/legion/templates/scout-assess-prompt.md"). Extract the parent directory path (everything before /templates/). Store this as LEGION_SKILL_DIR — you will use it for all template reads (e.g., {LEGION_SKILL_DIR}/templates/scout-assess-prompt.md).
What ships with it
9 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.
- templates/analyst-iteration-prompt.md 8.0 KB
- templates/completion-check-prompt.md 5.8 KB
- templates/delta-scout-prompt.md 3.2 KB
- templates/hardening-prompt.md 3.7 KB
- templates/impl-agent-prompt.md 2.5 KB
- templates/scout-assess-prompt.md 3.3 KB
- templates/simplifier-prompt.md 1.8 KB
- templates/verification-prompt.md 5.0 KB
- templates/wave-prep-prompt.md 4.1 KB
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.
- 9d ago First seen · 651 lines · 54 tokens per session scan B be96dd8b0bb6
legion is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 6,487 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
review-health
Audit any repository's structural health and file the findings as proposed epics and one-PR issues.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.