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 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/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/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="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.00064 | $0.02073 |
| Opus 5.5 | $0.00026 | $0.00829 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (62 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 2,073 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ai-agents-generation-and-release
Operate the ai-agents generation and release machinery, covering the seven buildall.py generators, generateagents.py, the drift gates, the version-free plugin manifests, and the npm publish path. Use when you say regenerate the mirrors, run the drift checks, why is the plugin version gate red, release the npm cli. Do…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
spk-admin-git-workflow
Operate Spec Kitty git workflows, worktrees, safe commits, merge preflights, stale state checks, and recovery.
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.