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 oreum-ai/smartstack --skill shipgit clone --depth 1 https://github.com/oreum-ai/smartstackWrote 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/oreum-ai/smartstack/ship)<a href="https://agentmods.dev/skills/oreum-ai/smartstack/ship"><img src="https://agentmods.dev/badge/skills/oreum-ai/smartstack/ship/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/oreum-ai/smartstack/ship"><img src="https://agentmods.dev/badge/skills/oreum-ai/smartstack/ship.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.00422 |
| Opus 5.5 | $0.00000 | $0.00169 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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 2mo 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
Skill: Ship
When to use
When a change is finished and you're ready to commit, push, or release. The final gate that makes sure you ship working, safe code — and that project memory is updated so the next session inherits your work.
Procedure (in order; stop at the first hard failure)
- Quality gate. Linter/formatter clean, type check clean, build succeeds. Tests green for any risky logic touched (auth/money/domain/integrity). A red test blocks shipping.
- Secret scan. Run
ai-rules/scripts/secret-scan.sh. No keys/tokens/passwords/.envvalues in the diff. If found: remove, rotate the secret, scrub history. Blocks shipping. - Rules pass. Quick self-check against the rule slices that apply. For non-trivial changes, run the
pr-reviewerskill. - Memory update. Run
ai-rules/scripts/session-save.shto write a detailed session summary (what changed, why, files, decisions, next steps); prune to the last few. - Error ledger. If any bug was fixed, record it (
scripts/error-log.sh); add a short common-errors entry if it's a recurring class. - Commit with a clear message. Conventional style:
feat:fix:refactor:chore:test:docs:- a concise description. One logical change per commit.
- Confirm the build runs for a demo/release: app starts, the happy path works end to end.
Commit message format
<type>: <what changed, imperative, concise>
<optional: why / what it fixes / follow-up>
Hard blocks (do NOT ship)
- Lint/type/build not clean, or a risky-logic test red/commented out.
- A secret is in the diff or history.
- Session memory wasn't updated.
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.
- 2mo ago First seen · 33 lines · 0 tokens per session scan A 5a40f8176826
ship is a skill published in the GitHub repository oreum-ai/smartstack (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 422 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.