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 sdcorejs/sdcorejs-agent --skill sdcorejs-shipgit clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWrote 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/sdcorejs/sdcorejs-agent/sdcorejs-ship)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-ship"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-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/sdcorejs/sdcorejs-agent/sdcorejs-ship"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-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.00099 | $0.05303 |
| Opus 5.5 | $0.00040 | $0.02121 |
| Sonnet 5.5 | $0.00020 | $0.01061 |
| Haiku 4.5 | $0.00010 | $0.00530 |
Grade A, and why
sdcorejs-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 16d 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path resolution: Resolve ../../_refs/... relative to this SKILL.md. Resolve another SDCoreJS skill by opening the sibling folder ../<skill-name>/SKILL.md.
Ship
Purpose And Boundary
Own the final delivery readiness boundary: prove the work satisfies the right contract, prove the branch hygiene evidence is current, and then hand off to artifact workflows only when the user explicitly asks for them.
sdcorejs-ship decides readiness. sdcorejs-git creates Git artifacts only
after current ship and branch-ready evidence exists and the user explicitly asks
for commit, PR, push, changelog, tag, or release artifacts.
sdcorejs-ship is responsible for:
- feature acceptance verification;
- bugfix verification;
- specless and docs-only hygiene verification;
- dependency-update safety verification;
- release readiness checks;
- final branch-ready checks;
- collecting evidence from explore, review, test, debug, repair-loop, and prior branch-ready contexts;
- producing
ship_context.
sdcorejs-ship is not responsible for:
- committing changes, creating PRs, pushing branches, tagging releases, publishing packages, or creating release artifacts directly;
- patching review/debug/test failures from read-only verify or branch-ready gates;
- silently installing tools or downloading probe tools;
- bypassing
sdcorejs-review,sdcorejs-test,sdcorejs-debug,sdcorejs-repair-loop,sdcorejs-git, orsdcorejs-explore.
Shared Protocols
Read ../../_refs/shared/runtime-protocols.md and
../../_refs/shared/artifact-lifecycle.md; consume and pass through the current
change's artifact_context. For production/release claims, also load
../../_refs/shared/ship-readiness-contract.mjs; it consumes the common approved
artifact, repository, source revision map, and evidence identities. Redact
suspected secrets before printing evidence. Read
../../_refs/shared/decision-coverage.md, preserve decision_coverage and
goal_backward_review, and block readiness when either reports an uncovered
record, invariant evidence gap, or unresolved critique blocker.
Preserve architecture_context and the exact architecture_gate. For required
architecture, verify the immutable spec -> architecture -> plan graph and
current INV-* conformance; missing/stale/mutated architecture or mismatched
path/hash/reference blocks readiness. A concrete not-applicable gate retains
architecture_context: null and must not be upgraded to PASS by inference.
Read ../../_refs/shared/validation-map.md; preserve the validation map's approved evidence evaluation. Read ../../_refs/shared/convergence-contract.mjs; verify-before-done evaluates and seals a receipt, while branch-ready verifies both against approved change/mode and current identity.
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.
- 16d ago Changed · +2 lines 4a152a9f48ed
- 25d ago Changed · -1 lines 8a2b282be233
- 2mo ago First seen · 503 lines · 99 tokens per session scan A e52e5366fddb
sdcorejs-ship is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 99 tokens to every session and 5,303 once invoked, about $0.0004 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 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
Fully automate a release with version-bump and childhood.
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.
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.