swarm-review

swarm-review is a skill for Claude Code, Codex from AnmarHani/SwarmVault. It costs 59 tokens per session (697 once invoked), scanned A, original, MIT.

A milestone review workflow that audits completed software work against its requirements and specification. It checks whether the requested behavior is implemented and properly tested, along with code quality and risks.

In plain words
What is it for?
Use it after a milestone, before starting the next one, or when asked to review completed work. It examines the milestone changes, tickets, requirements, tests, standards, and shipped user-facing text.
Why use it?
It catches missing requirements and weak tests that a linter, which mainly checks code patterns, would not detect.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after a milestone, before starting the next one, or when asked to review completed work. It examines the milestone changes, tickets, requirements, tests, standards, and shipped user-facing text.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anmarhani/swarmvault/swarm-review
Install

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.

Any agent
npx skills add AnmarHani/SwarmVault --skill swarm-review
Clone the repo
git clone --depth 1 https://github.com/AnmarHani/SwarmVault

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for swarm-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-review/github.svg)](https://agentmods.dev/skills/anmarhani/swarmvault/swarm-review)
Your own site
<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-review"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-review/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.

agentmods 80×15 button for swarm-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-review"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.00697
Opus 5 $0.00030 $0.00349
Sonnet 5 $0.00012 $0.00139
Haiku 4.5 $0.00006 $0.00070

Measured 9d ago against content hash e872488057e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

swarm-review 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 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.

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.

skills/swarm-review/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

swarm-review — the milestone gate

Reviews against the spec, not just the code — that is the difference between this and a linter. Expect a top-tier model; warn if the session runs less. Milestone cadence only (token economy): not per-commit.

Scope: the milestone's diff (git log since last sweep), its tickets, and its FR specs.

The four lenses, in order

  1. Fulfillment (the one that matters most): every Must-FR of the milestone, individually — no sampling. Are the acceptance criteria actually met? Do the tests assert the criteria (not just execute the code)? Is the FR → ticket → commit → test chain intact?
  2. Standards: naming, error handling (exceptions handled, not swallowed), comment discipline (light, constraint-stating), test quality (behavior asserted, not implementation), commit hygiene — audited against swarm-implement's references/clean-code.md where available, including its dogma traps: fragment soup, one-implementation abstractions, pattern theater, and SRP shrapnel are findings, not compliance. End-user text shipped in the milestone (UI strings, README, release notes, marketing) is audited against the project's voice.md and the audience firewall — load swarm-write for the criteria.
  3. Simplification: duplicated logic to merge, needless abstraction to delete, blocks that could be simpler or generalized. If a fix is obvious and small, still ticket it — see the rule below.
  4. Risk: input validation gaps, security smells, and a devil's-advocate pass — "what assumption, if wrong, hurts most?"

Findings

One per issue, compact (machine lane): severity (blocker/major/minor), FR link, file:line evidence, concrete suggested fix. Write the report to 30 Plans/<P>/reviews/M<N>-sweep.md (human-lane summary + machine-lane findings), then one ticket per accepted finding — findings that stay chat messages die in scrollback.

Never auto-fix. Reporting and fixing in the same pass corrupts the review; fixes are swarm-implement's job via the tickets.

Read the full file on GitHub · 58 lines

Changes

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.

  1. 9d ago First seen · 58 lines · 0 tokens per session scan A e872488057e0

Subscribe to this mod's changes

swarm-review is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 697 once invoked, about $0.0003 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-31.