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 Senpai-Sama7/autonomous-sdlc-command-center --skill ci-releasegit clone --depth 1 https://github.com/Senpai-Sama7/autonomous-sdlc-command-centerWrote 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/senpai-sama7/autonomous-sdlc-command-center/ci-release)<a href="https://agentmods.dev/skills/senpai-sama7/autonomous-sdlc-command-center/ci-release"><img src="https://agentmods.dev/badge/skills/senpai-sama7/autonomous-sdlc-command-center/ci-release.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.1 | $0.00027 | $0.00231 |
| Opus 5 | $0.00014 | $0.00115 |
| Sonnet 5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
ci-release 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 7d 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.
What it actually says
CI and Release Engineering
Normalize failures into: symptom, first failing boundary, likely cause, confirming evidence, smallest fix, regression test, and rollback condition. Use the portable readiness tooling (sdlc_release_readiness MCP tool, python mcp/sdlc_cli.py release-readiness, or scripts/commands/release_readiness.ps1 on PowerShell) to collect read-only delivery evidence before claiming a release is ready.
For release readiness, check versioning, changelog, tests, static analysis, dependency and license changes, migration safety, observability, rollback, and environment parity. Separate local evidence from remote CI evidence. A release recommendation must state what was not verified and whether a human approval is still required.
Do not retry blindly, suppress a failing check, weaken a quality gate, or publish artifacts without approval. Preserve useful logs while redacting secrets and unneeded customer data.
Machine-readable contract: contract.json. Behavioral evals: tests.md.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 15 lines · 27 tokens per session scan A 494d433f783c
ci-release is a skill published in the GitHub repository Senpai-Sama7/autonomous-sdlc-command-center (0 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 231 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
seed-snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
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…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…