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/OneWave-AI/claude-skillsWrote 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/plugins/onewave-ai/claude-skills/agent-army)<a href="https://agentmods.dev/plugins/onewave-ai/claude-skills/agent-army"><img src="https://agentmods.dev/badge/plugins/onewave-ai/claude-skills/agent-army/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/plugins/onewave-ai/claude-skills/agent-army"><img src="https://agentmods.dev/badge/plugins/onewave-ai/claude-skills/agent-army.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-army 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.
What it actually says
{
"name": "agent-army",
"version": "1.0.0",
"description": "Deploy a 2-layer parallel agent hierarchy for large, parallelizable work: big refactors, multi-file migrations, codebase-wide audits, and bulk generation. Pick an army size and power level; includes git checkpoints, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.",
"author": {
"name": "OneWave AI",
"url": "https://www.onewave-ai.com"
},
"homepage": "https://github.com/OneWave-AI/claude-skills/tree/main/plugins/agent-army",
"repository": "https://github.com/OneWave-AI/claude-skills",
"license": "MIT",
"keywords": [
"agents",
"multi-agent",
"orchestration",
"parallel",
"refactor",
"migration",
"claude-code"
],
"displayName": "Agent Army",
"icon": "./.claude-plugin/icon.png",
"documentationUrl": "https://github.com/OneWave-AI/claude-skills/blob/main/plugins/agent-army/README.md",
"supportUrl": "https://www.onewave-ai.com/contact",
"privacyPolicyUrl": "https://www.onewave-ai.com/privacy",
"termsOfServiceUrl": "https://www.onewave-ai.com/terms"
}
What ships with it
1 file beside plugin.json 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 · 28 lines scan A b96081339f89
agent-army is a plugin published in the GitHub repository OneWave-AI/claude-skills (342 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-03.
Other plugins, from other repositories
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
git
Version-control skills for the whole branch lifecycle: committing, worktrees, merge conflicts, undo/recovery, PR descriptions, changelogs, releases, and branch cleanup.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
dootask
A DooTask plugin toolkit for creating plugins, preparing releases, improving project instructions, and making Conventional Commits. Conventional Commits are a standard format for describing Git changes.
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.