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 fortunto2/rust-code --skill swarm-improvegit clone --depth 1 https://github.com/fortunto2/rust-codeWrote 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/fortunto2/rust-code/swarm-improve)<a href="https://agentmods.dev/skills/fortunto2/rust-code/swarm-improve"><img src="https://agentmods.dev/badge/skills/fortunto2/rust-code/swarm-improve/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/fortunto2/rust-code/swarm-improve"><img src="https://agentmods.dev/badge/skills/fortunto2/rust-code/swarm-improve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Rogue Agent · line 3 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00089 | $0.01396 |
| Opus 5.5 | $0.00036 | $0.00558 |
| Sonnet 5.5 | $0.00018 | $0.00279 |
| Haiku 4.5 | $0.00009 | $0.00140 |
Grade A, and why
swarm-improve 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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/swarm-improve — Multi-Agent Project Improvement
End-to-end workflow: plan → branch → delegate execution → verify.
This is a thin orchestrator. The heavy lifting is in /plan (analysis) and /delegate (execution).
Step 0: Validate Baseline
Before anything else:
cdto the project (absolute path — store it, you'll need it for every delegate)- Read
CLAUDE.mdorREADME.md→ find the test command - Run tests:
bash: make test(or equivalent)
If tests FAIL → HARD STOP. Create one P0 task "fix broken tests" and finish. Do NOT plan improvements on a broken project — all delegate work will fail too.
Step 1: Plan
If .tasks/PLAN.md already exists and is recent (< 24h):
- Read it, skip to Step 2
- Tell the user you're using the existing plan
Otherwise, run the /plan workflow inline (this skill has the same tools):
- Recon — already done in Step 0
- Design dimensions — pick 3+ analysis angles adapted to the goal (not hardcoded)
- Check agent availability — try each agent before committing to the plan
- Delegate to 3+ diverse agents — agent diversity mandatory (claude + gemini + codex preferred)
- Wait — poll every 60s with
delegate_status - Synthesize — cross-reference, dedup, create STAR-formatted execution tasks +
.tasks/PLAN.md
Use the task tool for all task creation — never write .tasks/ files manually. Files are named YYYYMMDD-NNN-slug.md automatically.
Step 2: Branch
bash: cd <absolute-project-path> && git checkout -b improve/swarm-$(date +%Y%m%d)
All delegate work happens on this branch. Master/main stays clean.
Step 3: Delegate Execution
Read .tasks/PLAN.md for the prioritized task list. Each task has STAR format — Action tells the delegate what to do, Result tells how to verify.
Assign agents by strength, diversify across agents:
| Task type | Primary | Fallback |
|---|---|---|
| Code changes, refactoring | claude | gemini |
| Quick fixes, single-file | codex | claude |
| Tests, docs | claude | codex |
| Review, analysis | gemini | opencode |
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.
- 1mo ago First seen · 115 lines · 89 tokens per session scan A dcf96e1ee5d7
swarm-improve is a skill published in the GitHub repository fortunto2/rust-code (46 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 1,396 once invoked, about $0.0004 per session on Opus 5.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
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
gemini-delegation
Delegates tasks to Gemini CLI implementing delegation-core for Google's models. Use when delegation-core selects Gemini or 1M+ token context is needed.
writing-git-commits
Write clear, focused Git commit messages and keep commits easy to review.
planner-task-packet
Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.