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.
git clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/ship)<a href="https://agentmods.dev/commands/niels-emmer/myace/ship"><img src="https://agentmods.dev/badge/commands/niels-emmer/myace/ship.svg" alt="Measured on agentmods" 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.00014 | $0.00348 |
| Opus 5 | $0.00007 | $0.00174 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
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 3d 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
Run through this before pushing or merging any change, even a small one. It should take under a minute for a small diff.
- Run it. Actually execute the code path you changed (run the app, run the relevant test, hit the endpoint) — don't rely on reading the diff and assuming it works.
- Glance at the full diff. Check for stray unrelated edits, leftover debug prints/console logs, and commented-out code that shouldn't ship.
- Scan for secrets. Make sure no API key, token, password, or
.envcontent snuck into the diff. If anything looks like a credential, pull it out before continuing. - Check the commit message. Does it clearly say what changed and, if not obvious, why?
- Decide push vs. PR. Low-stakes solo work on a feature branch: push/merge directly. Anything touching shared infra, production data, or something you're not fully confident about: open a PR instead (see the git-workflow skill).
- Confirm before
git pushif it targets a shared or default branch, or before any destructive command — this is a deliberate pause point, not a step to skip.
If any step surfaces a real problem, fix it first and re-run the checklist — don't ship past a known issue.
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.
- 3d ago First seen · 17 lines · 14 tokens per session scan A 02cbec2cf925
ship is a command published in the GitHub repository niels-emmer/myace (1 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 348 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-09-03.
Other commands, from other repositories
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
commit
Based on the above changes, create a single git commit.
devkit.github.create-pr
Creates a GitHub pull request with branch creation, commits, and detailed description. Use when you need to submit changes for review.
pr
Create a branch, split changes into logical commits, and open a pull request.
squash
Squash recent commits into a single clean commit.
amend
Amend the most recent commit with additional changes or an updated message.