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.
git clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/commands/sifxprime/kodelyth-ecc/swarm)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/swarm"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/swarm.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.1 | $0.00024 | $0.00818 |
| Opus 5 | $0.00012 | $0.00409 |
| Sonnet 5 | $0.00005 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
swarm 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/swarm
Run a parallel team of ECC specialists on the same task in isolated git worktrees coordinated by a tmux session. The generalized form of /devil-mode, /team-review, /security-audit, and /pre-release — pick any task, pick any agents, get N panes ready to attach.
Quick examples
/swarm audit oauth flow for security regressions
/swarm ship v2.0 --agents release-captain,security-reviewer,e2e-runner --execute
/swarm refactor payments module --agents 6 --harness codex --execute
/swarm production is down, auth service 502s --agents incident-commander,debug-detective,silent-failure-hunter --execute
Behavior
By default, prints the dry-run plan (safe to inspect). Add --execute to actually create worktrees, spawn the tmux session, and launch agents.
| Flag | Effect |
|---|---|
--task "..." |
Required (or use --plan plan.json). |
--agents N |
Smart-pick N specialists from task signals + baseline anchors + rotation. |
--agents name1,name2,... |
Explicit agent list. |
--harness claude|codex|opencode|windsurf|echo |
Launcher template (default claude). |
--seed <path> |
Overlay path from main repo into each worktree (e.g. --seed .env). |
--base-ref <ref> |
Branch base for all worktrees (default HEAD). |
--session <name> |
Override the auto-generated tmux session name. |
--replace |
Tear down any existing session/worktrees with the same names. |
--execute |
Create worktrees + tmux + launch agents. |
--write-only |
Just write coordination files without spawning. |
--json |
Print the full plan as JSON. |
Smart agent picking
If you pass --agents N (a number), the swarm picks specialists in this order:
- Signal-driven — task keywords match specialist (security →
security-reviewer, perf →performance-optimizer, API →api-guardian, …). - Baseline anchors —
code-reviewer+pair-programmerget added (every task benefits). - Rotation fill — 4/6/8-agent default rotations tuned for breadth.
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.
- 3d ago First seen · 69 lines · 24 tokens per session scan A 6e05f09944c8
swarm is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 818 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
pr
Create a clear, reviewer-friendly pull request for the committed work on the current branch. The PR itself is the artifact — produce no separate report. You never modify source files; your writes are git push and the PR. Every fact belongs in the PR title and body.
sync-pr-body
Bring the pull request description back in line with the code after correction rounds changed it. The description was written when the draft PR opened; corrections since then may have falsified specific claims in it. Your product is an accurate PR body — nothing else.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
refactor-workflow.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ship
Encodes the "stage and commit" ritual: verify (receipt gate) → scope → branch → write the commit message from what is actually staged → commit → push → open PR to the default branch → move the Jira issue to In Review. NO merge (merging is the reviewer's call). NO tag (deploys are project-specific and out of scope).
start-feature
Jalankan AI Agents Rogue end-to-end untuk permintaan user di chat ini (override mode ke e2e untuk tugas ini).