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/sdlcgit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00042 | $0.01320 |
| Opus 5 | $0.00021 | $0.00660 |
| Sonnet 5 | $0.00008 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
sdlc 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Master SDLC Orchestrator
This command runs the complete Software Development Lifecycle end-to-end with 5 phases, explicit approval gates between each phase, and handoff documents to keep context windows bounded.
Usage
/sdlc "build a user authentication system"
/sdlc "add OAuth login" --from Plan --to Build
/sdlc --phase Build # Re-run Build phase in isolation
Phases
The orchestrator runs agents sequentially across 5 phases:
- Plan →
/sdlc-plan(product-manager: grill interview + scope.json + PRD + issues) - Build →
/sdlc-build(ux-designer [if has_ui] + fullstack-engineer × slices + qa-engineer) - Verify →
/sdlc-verify(security-engineer + performance-engineer [if needs_performance_audit]) - Ship →
/sdlc-ship(devops-engineer) - Operate →
/sdlc-operate(sre-engineer + data-engineer [if has_data_pipeline])
9 agents total (product-manager, ux-designer, fullstack-engineer, qa-engineer, security-engineer, performance-engineer, devops-engineer, sre-engineer, data-engineer)
Process
- Parse feature request
- Create
./projects/<feature-name>/withdocs/,handoffs/subdirectories - Run Plan phase → product-manager interviews + produces scope.json + PRD
- GATE: "Ready to start Build?" → on confirm: run /handoff →
handoffs/plan-handoff.md→ invoke/sdlc-build - Build phase completes → GATE: "Ready to start Verify?" → on confirm: run /handoff →
handoffs/build-handoff.md→ invoke/sdlc-verify - Verify phase completes → GATE: "Ready to Ship?" → on confirm: run /handoff →
handoffs/verify-handoff.md→ invoke/sdlc-ship - Ship phase completes → GATE: "Ready to Operate?" → on confirm: run /handoff →
handoffs/ship-handoff.md→ invoke/sdlc-operate - Compile final summary
Phase Transition Flow
/sdlc-plan
└─ [GATE: "Ready to start Build?"]
└─ /handoff → handoffs/plan-handoff.md
└─ /sdlc-build
└─ [GATE: "Ready to start Verify?"]
└─ /handoff → handoffs/build-handoff.md
└─ /sdlc-verify
└─ [GATE: "Ready to Ship?"]
└─ /handoff → handoffs/verify-handoff.md
└─ /sdlc-ship
└─ [GATE: "Ready to Operate?"]
└─ /handoff → handoffs/ship-handoff.md
└─ /sdlc-operate
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 · 115 lines · 42 tokens per session scan A 36810237931a
sdlc is a command published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,320 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
team
The team command manages team members and messages for your Codev project. Team data is stored in codev/team/ and displayed in the Tower dashboard.
codev
The codev command manages project setup, maintenance, and framework-level operations.
tasks-to-ado
Convert existing tasks into actionable, dependency-ordered Azure DevOps work items for the feature based on available design artifacts.
sdlc-dev
Phase 3 — Development & Coding. Spawns 9 agents with 4 parallel groups: backend-engineer, frontend+mobile, database, fullstack-engineer.
sdlc-parallel
Run multiple agents in parallel across phases with shared context and collaboration.
sdlc-plan
Phase 1 planning — grill-me interview + 4 sequential agents (product-manager → business-analyst → software-architect → security-architect).