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/Kin9Zeus/senior-engineer-skillsWrote 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/kin9zeus/senior-engineer-skills/snr-ship)<a href="https://agentmods.dev/commands/kin9zeus/senior-engineer-skills/snr-ship"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-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/commands/kin9zeus/senior-engineer-skills/snr-ship"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-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.00029 | $0.00814 |
| Opus 5.5 | $0.00012 | $0.00326 |
| Sonnet 5.5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
snr-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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness Gate
Assess readiness to ship: $ARGUMENTS
Load release-readiness. Load the domain skills for anything that needs a
deeper look.
Produce one of three verdicts, in writing
GO No blockers. Ship.
GO WITH RISK Named, owned, accepted risks. Ship, with mitigations listed.
NO GO Named blockers. Do not ship until these close.
Never soften a NO GO into "mostly ready". If a blocker is real, say no in
the first sentence and name it. A gate that has never produced a NO GO is not
a gate.
Check the blockers first — any one is NO GO
These are not judgement calls. Each causes a breach, data loss or legal exposure the launch cannot be undone from.
- A secret in the repository or its git history
- Any user can access another user's data (test it: auth as A, request B's)
- No backups, or backups never restored
- Personal data processed with no policy, or a policy omitting a real processor
- No working data-deletion path where one is promised or required
- Payment amounts computed or trusted from the client
- A webhook that mutates state without verifying its signature
- String-interpolated SQL on a user-reachable route
- Debug mode on, or stack traces returned to clients
- No rollback path that anyone has ever executed
- A migration with no tested reverse running against production data
- A known critical vulnerability in a reachable dependency
If any are unticked, the verdict is NO GO and the report is short.
Then the full gate
Nine areas — security, data, legal/trust, public surface, accessibility,
correctness, operations, performance, documentation. The complete checklist with
verification commands is in references/launch-checklist.md.
Run the automated helpers where they apply:
skills/security-hardening/scripts/secret-scan.sh
skills/web-presence-audit/scripts/web-check.sh <url>
Capture the pre-launch baseline
Without it you cannot tell whether the post-launch numbers are bad.
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 First seen · 91 lines · 29 tokens per session scan A da26c0f9b366
snr-ship is a command published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 814 once invoked, about $0.0001 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 commands, from other repositories
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
sweep-mode-c-lifecycle
If Mode C was selected, the wave lifecycle is the back half of the issue-side lifecycle: no Curator, no Approval gate, no Builder. Each PR is routed by its current label to Judge, Doctor→Judge, or Merge directly.
release
Prepare and publish a GitHub release.
release-tag
Create and push a version tag after a release PR has been merged.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.