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 Mathews-Tom/armory --skill ship-workflowgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/ship-workflow)<a href="https://agentmods.dev/skills/mathews-tom/armory/ship-workflow"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/ship-workflow/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/mathews-tom/armory/ship-workflow"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/ship-workflow.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.00158 | $0.02258 |
| Opus 5.5 | $0.00063 | $0.00903 |
| Sonnet 5.5 | $0.00032 | $0.00452 |
| Haiku 4.5 | $0.00016 | $0.00226 |
Grade A, and why
ship-workflow 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 7d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Workflow
Ship through the authorized endpoint using the repository's current checks, required reviews, branch protections and merge policy. Routine shipping is the default. The executable owns Git/provider mutations, journals, reconciliation and cleanup; the assistant owns scope, logical change grouping, repository conventions and unfamiliar failure diagnosis.
Reference Files
| File | Contents | Load When |
|---|---|---|
references/commit-planning.md |
Inventory, logical commit plans and local gate packets | Creating commits or requesting local/per-commit validation |
references/lifecycle-contract.md |
Explicit policy, assurance, publication, stack packets, journals and recovery | Supplying --policy or --stack-plan, resuming, or interpreting a blocker |
references/project-detection.md |
Repository gate-source detection | Locating local test commands; version/changelog tables do not authorize release work |
Workflow
1. Resolve scope
Choose exactly one target: --pr N, --branch NAME, an explicit stack, a saved run, or the current branch when it identifies exactly one target. Resolve ambiguous targets or bases from provider/Git facts; ask only when those facts cannot decide. --repo [HOST/]OWNER/REPO names the PR base repository, and --head-repo OWNER/REPO names a fork head namespace.
| Request | Endpoint |
|---|---|
"Ship it", /ship, "finish PR 12 and clean up" |
clean (default) |
| "Merge it", "land PR 12 but keep the branch" | --until merged |
| "Open a PR", "push and PR" | --until pr |
| "Check CI", "what blocks PR 12" | --until pr --dry-run (inspection only) |
| Version, changelog, tag, release, package publication or deployment | Separate release authority, not this skill |
State the target, endpoint and cleanup scope before mutation. A resume preserves the saved authority. pr confirms publication only; merged adds confirmed landing and applicable post-merge acceptance; clean adds proof-based cleanup. Keep active, dirty, protected/default/release, unmerged, open-PR-dependent and unknown work. Never widen a stack selection or resume endpoint implicitly.
What ships with it
33 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CHANGELOG.md 14 KB
- evals/cases.yaml 12 KB
- references/commit-planning.md 11 KB
- references/lifecycle-contract.md 53 KB
- references/project-detection.md 5.8 KB
- scripts/changeset.py 99 KB runs code
- scripts/git_ops.py 123 KB runs code
- scripts/github_ops.py 146 KB runs code
- scripts/graph.py 117 KB runs code
- scripts/lifecycle.py 91 KB runs code
- scripts/native_stack.py 69 KB runs code
- scripts/publish.py 69 KB runs code
- scripts/ship.py 19 KB runs code
- scripts/state_store.py 77 KB runs code
- tests/conftest.py 217 B runs code
- tests/graph_world.py 38 KB runs code
- tests/test_changeset.py 65 KB runs code
- tests/test_cli_publication_selection.py 4.1 KB runs code
- tests/test_cli_stack_plan.py 35 KB runs code
- tests/test_execution.py 38 KB runs code
- tests/test_git_ops.py 83 KB runs code
- tests/test_github_ops.py 166 KB runs code
- tests/test_graph_execution.py 73 KB runs code
- tests/test_graph_git.py 38 KB runs code
- tests/test_graph_journal.py 44 KB runs code
- tests/test_graph_plan.py 21 KB runs code
- tests/test_lifecycle.py 26 KB runs code
- tests/test_native_landing.py 13 KB runs code
- tests/test_native_process_crash.py 3.8 KB runs code
- tests/test_native_stack.py 45 KB runs code
- tests/test_publication.py 92 KB runs code
- tests/test_retarget.py 18 KB runs code
- tests/test_state_store.py 59 KB runs code
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.
- 7d ago Changed · -72 lines 8c6bdcef498b
- 8d ago Changed · -38 lines · +87 tokens per session 9e3724bdcb23
- 1mo ago First seen · 217 lines · 71 tokens per session scan A 825006b024b9
ship-workflow is a skill published in the GitHub repository Mathews-Tom/armory (334 stars, last pushed 2d ago), licensed MIT. It adds 158 tokens to every session and 2,258 once invoked, about $0.0006 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-09-05.
Other skills, from other repositories
release
Release management and versioning toolkit for the wicked-garden plugin. Automates changelog generation, semantic versioning, and version bumping from git history. Use when preparing releases, generating changelogs, or managing plugin versions.
wicked-garden-platform-gh-cli
Use when you need gh CLI patterns beyond the basics — debugging failed workflow runs, bulk PR operations, release automation, or repo health checks. Provides composable gh invocations for power users. NOT for simple git commands (use Bash) or GitLab (use the glab-cli skill). Use when: "debug the failed workflow run"…
wicked-garden-platform-glab-cli
Use when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash).
safe-public-release
Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory…
mx-pr
Draft a pull request from the feature spec and git log, then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
release-pr-quality-gate
Build an AgentWorks release or pull-request browser quality gate over saved suites and exact build identity. Use when a merge, deployment, or promotion needs an auditable QA decision.