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 agentmods add skills/rafmacalaba/armada/armada-verificationnpx skills add rafmacalaba/armada --skill armada-verificationgit clone --depth 1 https://github.com/rafmacalaba/armadaWrote 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/rafmacalaba/armada/armada-verification)<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-verification"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-verification.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 | $0.00017 | $0.00286 |
| Opus 5 | $0.00009 | $0.00143 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
armada-verification 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 4d 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
Armada Verification
Pre-completion verification rules for all Armada agents (Galleon, Clipper, Corvette, etc.) before returning a task receipt to Commodore.
Verification Checklist
Before reporting done, FIX READY, or PASS, every subagent MUST complete and paste evidence for:
- Lint & Typecheck: Run linting and typechecking tools. Paste command and log tail in receipt
Evidence. - Unit / Component Tests: Run affected test suites. Paste command and passing transcript in receipt
Evidence. - TDD / Regression Check: Verify Red -> Green transition. For defect fixes, include the test that would have caught the regression.
- Real API / Service Check (Backend): Exercise changed endpoints with real requests and responses. Include status codes and JSON payloads.
- Persistence Check (Data Changes): Confirm data changes persist across server/service restarts.
- Visual / Render Check (Frontend / QA): Capture screenshot or verify rendered UI. Paste screenshot path under
armada/screenshots/.
No Evidence = QA Rejection
Any task returned without pasted terminal log output, test tails, or screenshot paths in the Evidence block of the Receipt will be rejected immediately by Commodore and QA.
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.
- 4d ago First seen · 24 lines · 17 tokens per session scan A 99f800501a56
armada-verification is a skill published in the GitHub repository rafmacalaba/armada (92 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 286 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-08-30.
Other skills, from other repositories
aoe
Use when launching, monitoring, or controlling AI coding agents (Claude Code, Codex, OpenCode, etc.) in tmux via Agent of Empires (aoe). Covers creating sessions, capturing agent output, running parallel worktree agents, and organizing work into groups and profiles. Prefer aoe over raw tmux for agent management.
aoe
Manage AI coding agent sessions via Agent of Empires (aoe).
debate
Structured adversarial analysis protocol. Quick single-agent modes (challenge, panel, pre-mortem, red team) plus a decision-review protocol where one agent proposes, one critiques, the proposer revises, and a binding/advisory judge panel decides ADOPT/REVISE/REJECT/ESCALATE.
update-to-latest
Safety-critical operational pipeline for analyzing and executing OpenCode/OMO updates with explicit approval, patch preservation, rollback capability, and evidence-state discipline.
patch-tracker
Track and verify custom patches to external dependencies. Register, audit, and verify patches survive updates. CRUD lifecycle for patch entries with post-update verification.
reader-report
Reader-first writing for any deliverable a human reads to understand a result: HTML reports, MD design docs, debate-result summaries, survey dashboards, executive briefs, handoff notes, panel-review syntheses. Writes for a reader who has NOT read the preceding material. NOT for: bug reports, incident reports, status…