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/loiane/specs-driven-development-spring-angular/shipping-and-launchnpx skills add loiane/specs-driven-development-spring-angular --skill shipping-and-launchgit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/shipping-and-launch)<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/shipping-and-launch"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/shipping-and-launch.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 | $0.00064 | $0.02073 |
| Opus 5 | $0.00032 | $0.01037 |
| Sonnet 5 | $0.00013 | $0.00415 |
| Haiku 4.5 | $0.00006 | $0.00207 |
Grade A, and why
shipping-and-launch 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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipping and launch
Faster is safer. Small, reversible, observable changes ship more often and break less.
What this skill produces
The artifact .specs/<feature-id>/09-ship-plan.md, populated from .claude/templates/ship-plan.template.md, with these sections filled in:
- Pre-ship gate results (PASS/FAIL per gate; FAIL = halt).
- Feature-flag posture (flag name, default, kill-switch, owner).
- Migration safety (Flyway/Liquibase script list, expand-vs-contract classification, rollback procedure).
- Observability sign-off (new metrics, structured-log keys, alert rules, dashboard link).
- Rollback plan (revert commit; DB rollback or contract-step procedure; on-call escalation).
- Staged rollout plan (canary → percentage steps → 100%).
- Release notes (user-facing changelog excerpt + internal notes).
Pre-ship gates (must all be green)
| Gate | Source of truth | Halt if |
|---|---|---|
| Validation | 07-validation-report.md verdict |
not PASS |
| Code review | 08-code-review.md verdict |
not Approve (or Approve with waivers linking ADRs) |
| Open questions | 01-spec.md, 03-design.md ## Open Questions |
any unresolved Q-NNN |
| Baseline regression | .specs/_baseline.json vs latest harness |
any new failure not in baseline |
| Diff scope | git diff origin/main...HEAD |
files outside any task's files_in_scope |
If any gate halts, stop and tell the user which command to run (/build, /test, /validate, or /review). Do not write a partial ship plan.
Feature flags
For any change that adds or alters a runtime path, decide:
- Flag required? Yes if the change is risky, irreversible, or touches a hot path. No if it's a pure bug fix or strictly additive.
- Default? Off in production until the canary clears. On in non-prod.
- Kill-switch? A documented config knob (env var or remote config key) that disables the new path without a redeploy.
- Owner? A named human (not "the team").
Record this in the ship plan even if the answer is "no flag" — with the reasoning.
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.
- 4d ago First seen · 154 lines · 64 tokens per session scan A 9708bf6f9460
shipping-and-launch is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 2,073 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ci-validation-gates
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22.
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…