Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/anshss/shiploopnpx agentmods add commands/anshss/shiploop/pushWrote 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/commands/anshss/shiploop/push)<a href="https://agentmods.dev/commands/anshss/shiploop/push"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/push/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/commands/anshss/shiploop/push"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/push.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.00000 | $0.02447 |
| Opus 5.5 | $0.00000 | $0.00979 |
| Sonnet 5.5 | $0.00000 | $0.00489 |
| Haiku 4.5 | $0.00000 | $0.00245 |
Grade A, and why
push 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shiploop:push
The push direction of the harness-code update channel. Reconciles the hub against improvements
you've made locally to mechanism scripts inside THIS workspace. Think of it as git push for
harness code: sync-port.sh is the machinery (already generalized in v1.2.0), this command wraps
it into a one-command action for interactive use.
Companion to /shiploop:update (pull). The two commands close the loop on fleet drift.
What it does (procedure)
- Preconditions:
GOVERN_UPSTREAM_HARNESS_REPOset inworkspace.sh; the workspace scaffolded from v1.2.0 or later (soscripts/govern/sync-port.shis present); a local hub clone reachable. - Drift detection via
scripts/govern/sync-templates.sh --check— mirrored files you've changed vs the last sync marker. - If drift → invoke
scripts/govern/sync-port.sh(the existing porter). It:- Cuts a branch off
origin/mainin the hub clone. - Spawns a headless porter that genericizes your changes (strips your identity strings, adds
placeholders like
__META_NAME__,__GITHUB_ORG__). - Validates:
bash -non changed shell files + forbidden-identity-strings gate on ADDED lines + scaffold-test-suite baseline diff. - On any gate failure, files an escalation and exits non-zero. NEVER pushes an unvalidated port.
- On pass, opens a PR against the canonical hub for HUMAN review — routing by your access
posture (see below): a same-repo PR when you can push to the hub, otherwise a cross-repo PR from
your fork (auto-created via
gh repo forkwhen you don't already have one).
- Cuts a branch off
- Report the PR URL (if any) and the marker state.
The three access postures (push v2 — the contribution funnel)
sync-port.sh derives where the branch lands and where the PR opens from git + GitHub, not from
workspace config — it reads the templates clone's origin, finds the canonical hub as that repo's
parent (falling back to origin itself when there is no parent), and checks your push permission.
So the PR always targets the real canonical hub, never stranding inside your own fork:
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 Changed · +1 lines f3a73bf3bffb
- 1mo ago First seen · 184 lines · 0 tokens per session scan A 1dc123502837
push is a command published in the GitHub repository anshss/shiploop (9 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,447 tokens. 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.