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-voyage-finishgit 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-voyage-finish)<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-voyage-finish"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-voyage-finish/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-voyage-finish"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-voyage-finish.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.00058 | $0.00445 |
| Opus 5.5 | $0.00023 | $0.00178 |
| Sonnet 5.5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
armada-voyage-finish 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: Voyage Finish
The finalization ritual one voyage closes. Loaded by the orchestrator at voyage-end, then dispatched to a galleon subagent as its task prompt. One-shot, ordered, PR-first.
Steps (strict order, stop on failure)
- Rebase.
git fetch originthengit rebase origin/master. Fast-forward only. If not a fast-forward, STOP and report to the orchestrator — never force-rebase, never merge. - TODO PR fix. For each feature this lane shipped, replace its
(#<pending>)placeholder inTODO.mdwith(#<PR>)using the real PR number fromgh pr view --json number. - Regen scaffold.
node src/cli.js init --from-armada armada/armada.yaml --target <lane>soAGENTS.md,REQUIREMENTS.md, and agents stay in sync withsrc/. TheAGENTS.mdvoyage header must not be re-titled. - Commit + push. Commit the regen + TODO fix on the lane branch and push to origin. Never commit on master.
- Open/update PR.
gh pr create --base master --title ... --body ...(orgh pr editif the PR already exists). Record the PR URL.
Forbids
- Never edit
armada/REQUIREMENTS.md. - Never close the voyage or mark any feature done.
- Never
git mergelocally, never push master directly. - Never run
npm publish. - Never edit files owned by other voyages or running phases.
Example: dispatch a galleon with this whole body as its task prompt; it executes step 1-5 and returns either a PR URL or the blocker that stopped it.
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 · 26 lines · 0 tokens per session scan A 91027ecb7ed0
armada-voyage-finish is a skill published in the GitHub repository rafmacalaba/armada (104 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 445 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
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
finishing-a-development-branch
Use when implementation is complete, tests pass, and you need to decide the integration path. Also use when asked to prepare a branch for release: 'update changelog', 'bump version', 'bump patch version', 'make sure changelog is correct', 'make sure version is correct'. Triggers: 'done with this branch', 'ready to…
context-mode-ops
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters…
git-release
Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable gh release create command. Use when preparing a tagged GitHub release.