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 rafmacalaba/armada --skill armada-ledgergit 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-ledger)<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-ledger"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-ledger/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/rafmacalaba/armada/armada-ledger"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-ledger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00368 |
| Opus 5.5 | $0.00021 | $0.00147 |
| Sonnet 5.5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
armada-ledger 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.
What it actually says
Armada: Ledger Routing
Every finding goes to exactly one ledger. Write to the wrong ledger and it will be ignored. Per-feature ledgers live under armada/ledgers/<feature>/.
Rules
- DEFECTS.md — for test failures, regression bugs, UI defects. Found by corvette (qa) during testing. Format: DEF-001, status OPEN, steps to reproduce.
- ADVERSARIAL_REVIEW.md — for hostile review findings. Found by xebec (adversary) during gate review. Format: ADV-001, Disposition PENDING.
- SECURITY_FINDINGS.md — for security vulnerabilities, injection vectors, auth bypasses. Found by frigate (security). Format: SEC-001, severity + CWE.
- Lifecycle: DEFECTS: OPEN -> FIX-READY -> CLOSED (corvette only). ADVERSARIAL: PENDING -> ACCEPTED/DISPATCHED -> CLOSED (via corvette). SECURITY: OPEN -> FIX-READY -> CLOSED.
- Only qa writes to DEFECTS.md (except orchestrator for status updates). Only adversary writes to ADVERSARIAL_REVIEW.md. Only security writes to SECURITY_FINDINGS.md.
Example: A failing unit test goes to armada/ledgers/my-feature/DEFECTS.md as DEF-003. An injection vector goes to armada/ledgers/my-feature/SECURITY_FINDINGS.md as SEC-001.
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 · 19 lines · 0 tokens per session scan A 99e8f1790129
armada-ledger is a skill published in the GitHub repository rafmacalaba/armada (104 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 368 once invoked, about $0.0002 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
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
simplify
Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with /simplify or /simplify .
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
review-team
Use when assigned a review or when an authored review boundary is reached.
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…