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 lacvietanh/akidevrule --skill akishipgit clone --depth 1 https://github.com/lacvietanh/akidevruleWrote 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/lacvietanh/akidevrule/akiship)<a href="https://agentmods.dev/skills/lacvietanh/akidevrule/akiship"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akiship/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/lacvietanh/akidevrule/akiship"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akiship.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00120 | $0.02511 |
| Opus 5.5 | $0.00048 | $0.01004 |
| Sonnet 5.5 | $0.00024 | $0.00502 |
| Haiku 4.5 | $0.00012 | $0.00251 |
Grade A, and why
akiship 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
akiship — one-command full release
Invoke with /akiship or an explicit release order, only as described in § Activation gate below. Goal: replace the daily hand-typed ritual ("resolve leftovers, sync every doc, lint, fix drift, changelog, commit, release…") with one invocation that runs to completion or stops once, early, with every blocker in a single batch.
CRITICAL — MANDATORY LOAD, BEFORE ANY OTHER TOOL CALL OF THE RUN (execute AND consult mode)
This skill sequences; it owns no content. The checklist is RULE-release.md (B5 migration doctrine, B7 fail-closed gate, B8 autonomy contract, B10 CI, B11 post-deploy verification) and doc sync is RULE-docs.md. Both are installed at ~/.aki/akidevrule/.
Read~/.aki/akidevrule/RULE-release.mdIN FULL and~/.aki/akidevrule/RULE-docs.mdas the FIRST tool calls after this skill loads. Keyword routing, memory of an earlier session, this file's summary, and a rule that happens to be in context do NOT count as loading — only aReadperformed in THIS run does.- Emit as the first line of the run:
[RULES] agent (core) + release,docs (akiship). If either file could not be read, say so and the run STOPS there. - A run that starts Phase 1 without those two
Readcalls is INVALID: every finding, commit, tag and deploy it produces is unauthorized and MUST be reported as such. Compliance is checked against the tool-call log, never against the receipt line (agent.B2).
If a step in this file disagrees with the rule file, the rule file wins — except the activation gate below, which this skill owns outright (pattern.A1) and which no rule file, keyword list, or routing table may widen.
Activation gate — two conditions, both required, checked before anything else
1. Release order. The current user turn carries either the exact token /akiship, or a turn explicitly ordering the release ritual for this repo, in any wording (worked examples in the table below). A completion-intensity phrase with no release object activates nothing: it names no ritual, so it is ordinary vocabulary about finishing something, not an order to run this skill. Seeing this file, or release.B8, in context is not an invocation either: being loaded is not being called.
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.
- 5d ago Changed ce33885e2653
- 25d ago Changed b42c82a9d4cc
- 28d ago Changed · +3 lines 80a250e82265
- 29d ago Changed · -22 tokens per session d57efd0a08d8
- 1mo ago Changed · +12 lines 3243a0344d62
- 1mo ago Changed · +4 lines · +142 tokens per session 2963b2e2ea9a
- 1mo ago Changed · +1 lines 35d90e515fd1
- 1mo ago Changed 324bd8e3d9be
- 1mo ago First seen · 55 lines · 0 tokens per session scan A b00e868da732
akiship is a skill published in the GitHub repository lacvietanh/akidevrule (10 stars, last pushed 5d ago), licensed MIT. It adds 120 tokens to every session and 2,511 once invoked, about $0.0005 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-31.
Other skills, from other repositories
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
starfleet-sessions
Ship session and workspace management — spawning ships, session attach/stop, git worktrees, web console, deployment. Load when launching/administering ships or managing the fleet web console.
starfleet-github
GitHub PR/CI/backport interaction via starfleetctl (read-only + mutating commands, PR claims, backports). Load when checking PR status/CI, claiming a PR branch, submitting or repairing a PR, or backporting.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…