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/eddiebelaval/squireWrote 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/eddiebelaval/squire/editorial-swarm)<a href="https://agentmods.dev/commands/eddiebelaval/squire/editorial-swarm"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/editorial-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.00000 | $0.01797 |
| Opus 5 | $0.00000 | $0.00898 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
editorial-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 8d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/editorial-swarm - Six-Agent Parallel Editorial Pipeline
Trigger when: the user wants to polish long-form prose — articles, essays, white papers, release notes, Shipped. magazine drafts, Bible essays, founding documents. Not for code, not for short social posts.
You are running the 6-agent editorial swarm on a prose draft. The goal: take a B+ draft to A-grade through parallel expert review, iterate on feedback, and stop when the rubric hits the target score.
Philosophy: one pass can't catch everything. Six specialists in parallel — each with a narrow brief — catches structural, voice, factual, narrative, line, and adversarial issues simultaneously. A merger agent resolves non-conflicts, Claude surfaces conflicts for user decision, then we iterate.
Source: Claude Code Insights Report - 2026-04-22. The pattern was already in use informally; this command codifies it.
Arguments
Parse $ARGUMENTS:
<draft-path>(required) — path to the markdown draft to polish--target <score>— rubric target, default9. Range 1-10.--max-iterations <n>— hard cap on iteration rounds, default3. Prevents runaway loops.--skip <agents>— comma-separated list of agents to skip (e.g.,--skip factcheck,skepticfor fiction).--dry-run— run one pass, output feedback, do not apply edits. Useful for first-read assessment.--quiet— only report final result + changelog, not per-agent output.
If no path is provided, error out with usage.
Step 0: Pre-flight
- Confirm the draft file exists and is a
.mdor.mdxfile. If it's a.txtor code file, refuse with "editorial-swarm is for prose drafts, not code — did you mean /polish?" - Read the full draft into context. Record word count.
- Detect draft type from path + frontmatter:
shipped/**→ magazine piece, applyvoice: narrative + literaryknowledge/**/raw/**→ research essay, applyvoice: scholarly + groundedproducts/**/VISION.md|SPEC.md|BUILD.md→ triad doc, applyvoice: doctrine + precise- default →
voice: professional + clear
- Snapshot the original:
cp <draft> <draft>.pre-swarm.bakso the user can diff or restore.
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.
- 8d ago First seen · 166 lines · 0 tokens per session scan A 870b3d50510f
editorial-swarm is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,797 tokens. 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 commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.
archivar
Archivar specs completadas y sincronizar delta specs con specs principales.