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 commands/saitarrun/devforge-ai/sdlc-shipgit clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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/commands/saitarrun/devforge-ai/sdlc-ship)<a href="https://agentmods.dev/commands/saitarrun/devforge-ai/sdlc-ship"><img src="https://agentmods.dev/badge/commands/saitarrun/devforge-ai/sdlc-ship.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.00030 | $0.00775 |
| Opus 5 | $0.00015 | $0.00387 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
sdlc-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 3d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-ship — Phase 4: Ship
Deploy to production via CI/CD, provision cloud infrastructure, and execute the release plan.
Execution
STEP 1: Read Verify Handoff
Read ./projects/<feature-name>/handoffs/verify-handoff.md to establish clean context — what was verified, findings resolved, and what is approved to ship.
STEP 2: Spawn devops-engineer
Spawn: Agent({
subagent_type: "fork",
name: "devops-engineer",
description: "DevOps Engineer (Ship phase) — CI/CD, cloud infra, release",
prompt: "[verify-handoff.md + scope.json]
Using the verified build context:
1. CI/CD Pipeline
- GitHub Actions workflow: lint → type-check → test → SAST → build → push
- Presubmit gates block merge on any failure
- Docker images built + pushed to registry (tagged with git SHA)
2. Cloud Infrastructure (Terraform)
- VPC + networking
- EKS/ECS cluster
- RDS with encryption + multi-AZ
- IAM roles (least privilege)
- Secrets Manager for credentials
- CloudWatch / logging configured
3. Kubernetes Manifests
- Namespace, Deployments, Services, Ingress
- ConfigMaps for env vars, HPA for auto-scaling
- Resource limits set on all containers
4. Release Execution
- Semantic version tag applied
- CHANGELOG.md updated
- Canary rollout: 5% → 30 min monitor → 50% → 100%
- Rollback procedure documented + tested in staging
5. Write ./projects/<feature-name>/docs/05-pipeline.log summarising
all CI checks, deploy steps, and release notes.
Output: ./projects/<feature-name>/deployment/"
})
Wait for devops-engineer to complete.
STEP 3: Display Completion
✅ Phase 4 — Ship Complete!
📁 Artifacts:
deployment/
.github/workflows/ci-cd.yml
docker/docker-compose.yml + Dockerfiles/
k8s/ (namespace, deployments, services, ingress, configmaps)
terraform/ (VPC, EKS, RDS, IAM, Secrets Manager)
docs/05-pipeline.log
✅ devops-engineer → CI/CD pipeline, cloud infra, release executed
Pipeline: ✅ green | Deploy: ✅ canary complete | Rollback: ✅ tested
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.
- 3d ago First seen · 102 lines · 30 tokens per session scan A d8717f9903b5
sdlc-ship is a command published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 30 tokens to every session and 775 once invoked, about $0.0002 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 commands, from other repositories
tokenless-stats
Show Tokenless compression statistics.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
cadence-handoff
Scaffold a SESSION handoff doc with machine facts pre-filled.
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
hep-local.body
Update fallback: 자동 업데이트가 안 되면 hephaestus update를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.