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-prgit 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-pr)<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-pr"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-pr/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-pr"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-pr.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.00037 | $0.00276 |
| Opus 5.5 | $0.00015 | $0.00110 |
| Sonnet 5.5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
armada-pr 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: PR-First Finish
The final step before reporting a feature lane done is creating a pull request. Never merge locally, never push master directly. The PR URL is the proof of delivery.
Rules
- Create the PR from the lane branch:
gh pr create --base master. Include a summary of changes and evidence links. - Never
git mergelocally. Nevergit push origin master. The PR is the only path to integration. - Write the PR URL into
armada/state/active.jsonfieldprUrl. Example:"prUrl": "https://github.com/owner/repo/pull/42". - If a PR is genuinely blocked (no remote, no permissions), state "PR blocked: " and report it to the commodore. Do not claim done without a PR URL or a stated blocker.
- Do not close or merge the PR yourself. The human partner reviews and merges.
Example: gh pr create --base master --title "feat: skills expansion wave 2.5" --body "Phase 1-3 evidence attached."
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 cf67b0e4b5d6
armada-pr is a skill published in the GitHub repository rafmacalaba/armada (104 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 276 once invoked, about $0.0001 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]…
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.
distilling-prs
Use when triaging, categorizing, or summarizing PR changes to decide where human attention should go. Triggers: 'summarize this PR', 'what changed in PR #X', 'triage PR', 'which files need review', 'PR overview', 'categorize changes', or pasting a PR URL. NOT for: judging code quality or producing findings on a branch…
reviewing-prs
Load before dispatching any subagent to review or triage a pull request, to pick the correct file version for the branch and worktree state. Required by: advanced-code-review (PR mode), code-review (--pr), distilling-prs (Phase 2), each of which names this skill at its dispatch point. Also use directly when: 'review…
requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
verify-built
Stage-1 acceptance verification — requirements-alignment check between the active plan/spec and the actual implementation diff, producing a GAP ledger bound to a commit digest. Use before accepting, PR-ing, or handoff-packaging any implementation work. Empirical QA and human-facing acceptance reports are later stages…