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 agentmods add skills/leifericf/agentic-sdk/shipnpx skills add leifericf/agentic-sdk --skill shipgit clone --depth 1 https://github.com/leifericf/agentic-sdkWhat 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 | $0.00017 | $0.00763 |
| Opus 5 | $0.00009 | $0.00381 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship
Role: the release cut. Takes the current tip to a tagged release: verifies the pre-land lanes, writes the changelog, assesses release risk, tags, and advances trunk. Folds the old merge-to-trunk and prepare-release steps into one cycle.
Prerequisites
~/.agentic-sdk/<project>/project.edn exists with :lanes :pre-land and :vcs. The tip
is at a state the maintainer wants to release. A target version (or a
recommendation the maintainer approves at the gate).
Procedure
- Verify the pre-land lanes. Dispatch one verifier running
verify-lanes against the
:pre-landlane set from the descriptor. This is the release gate: it must pass clean. FAIL feeds back to fix-bug or implement-change; the release does not proceed on a failing gate. - Write the changelog (if the project keeps one). Dispatch write-changelog. It checks the project stage first: alpha and beta projects keep no changelog, and the dispatch returns immediately with no entry. For stable projects it reads the commit log since the last release tag, groups changes by category, drops internal-only churn, and writes the release section. Determine the version bump from the landed changes: breaking changes force major, new capabilities force minor, fixes force patch. Recommend; the maintainer decides at the gate.
- Assess release risk. Dispatch assess-risk against the landed
changes. It maps the blast radius, dependencies and their failure
behavior, the rollout strategy, monitoring and rollback plan, the
risk register, and the go/no-go criteria. It writes
ops/<date>_risk_<slug>.md. Hold its one-line return. - Advance trunk, then tag. The tip is a linear stack ready to
land. Advance the protected main bookmark over the stack: with jj,
jj bookmark set main -r <tip>, then push. This is the merge-to-trunk step folded in. Then tag at main: with jj (git-compatible),git tag -a v<version> -m "<version>"and push the tag. - Present the gate. Show the maintainer the changelog (if any), the risk assessment path, the recommended version, and the tag. The tag is the approval gate. On approval, apply the tag and advance trunk. An autonomous run never tags or advances main without the maintainer's yes.
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.
- 2d ago First seen · 69 lines · 17 tokens per session scan A 737d2fac5ab4
ship is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 763 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-08-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.