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 agentmods add commands/iolairus/borderlint/shipgit clone --depth 1 https://github.com/iolairus/borderlintWhat 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 | $0.00016 | $0.00396 |
| Opus 5 | $0.00008 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
ship 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 2d 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
Ship the change $ARGUMENTS (or the one inferred from the current branch — strip a leading Jira key like PROJ-123- before matching against openspec/changes/). This is the closing gate of the pipeline; every step must pass before the next runs.
Steps
-
Validate —
openspec validate <change> --strictand confirm every task intasks.mdis checked. Fail fast otherwise. -
Archive — run
/opsx-archivefor the change so delta specs merge intoopenspec/specs/. Commit the archive result on the feature branch withchore(<change>): archive openspec change. -
Merge — read
workflow.yamlfor platform, integration branch, and work mode:- On a feature branch, with
gh/glaband an open PR: check CI/approval status; if green, merge (squash by default — confirm strategy with the user the first time) and delete the remote branch. Without CLI: instruct the user to merge in the web UI, and wait for confirmation. - Directly on the integration branch (flexible mode): there is no PR — just push (
git pull --rebase && git push). Warn that this skips code review.
- On a feature branch, with
-
Close the loop —
- If on a feature branch:
git checkout <integration_branch> && git pull, delete the local feature branch. - Update the linked task:
status: done. - If the task's
idis a real Jira key, remind the user to transition the Jira issue (we don't have API access).
- If on a feature branch:
-
Report: change archived, work merged, task closed — and list any follow-up tasks from the same discovery still pending.
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.
- 2d ago First seen · 23 lines · 16 tokens per session scan A 9d202ee82bdf
ship is a command published in the GitHub repository iolairus/borderlint (7 stars, last pushed 10d ago), licensed MIT. It adds 16 tokens to every session and 396 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.