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-securitygit 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.00026 | $0.00516 |
| Opus 5 | $0.00013 | $0.00258 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
sdlc-security 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.
What it actually says
Security Patching & Hardening Command
This command conducts automated security scans, updates vulnerable dependencies, resolves OWASP Top 10 vulnerabilities, and applies enterprise cryptographic and network security hardening.
Usage
/sdlc-security --audit-only # Full security & CVE audit report
/sdlc-security --fix-cves # Automatically patch known CVEs and update dependencies
/sdlc-security --harden-headers # Inject enterprise HTTP security headers
/sdlc-security --protocol zero-trust # Implement mTLS and JWT authorization checks
/sdlc-security "Fix IDOR in claim endpoint" # Surgically fix specific reported vulnerability
Process
- Vulnerability & CVE Discovery:
- Executes SAST scans,
npm audit/snyk, and OWASP rule evaluations across all service layers.
- Executes SAST scans,
- Surgical In-Place Remediation:
- Updates vulnerable dependencies or overrides transitive package versions.
- Refactors insecure code patterns (SQL injection, XSS, insecure deserialization, IDOR).
- Protocol & Security Header Hardening:
- Injects HSTS, CSP, rate-limiting middleware, and TLS 1.3/AES-256 encryption standards.
- Regression & Safety Verification:
- Verifies the application build, tests, and API contracts against breaking changes.
Output Format
### 🛡️ Security Patching & Hardening Report
**Action**: Dependency CVE Remediation & Security Header Hardening
#### 🔒 Vulnerabilities Patched
- **CVE-2024-XXXX**: Upgraded `jsonwebtoken` from `8.5.1` -> `9.0.2` (High Severity)
- **OWASP A01 (Broken Access Control)**: Added tenant ownership validation to `/api/v1/claims/:id`
- **Security Headers**: Configured HSTS, CSP, and X-Content-Type-Options middleware
#### ✅ Verification
- Unit & Regression Tests: 142/142 Passed
- Typecheck: 0 errors
- Security Audit: 0 Critical / 0 High vulnerabilities remaining
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 · 49 lines · 26 tokens per session scan A 629cc9ca65f3
sdlc-security is a command published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 26 tokens to every session and 516 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 commands, from other repositories
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).
sdlc-ops
Phase 6 — Operations & Monitoring. Spawns sre-engineer, secops-analyst, data-engineer, release-manager (all in parallel).
sdlc-test
Phase 4 — Testing & Security. Spawns qa-manual-tester, automation-qa-engineer, appsec-engineer, penetration-tester, performance-engineer.
sdlc-deploy
Phase 5 — Infrastructure & Deployment. Spawns devops-engineer and cloud-engineer to design CI/CD, containerization, and cloud infrastructure.