sdlc-test

A command that creates and runs different levels of automated software tests, from small unit tests to browser, performance, failure, and security tests. It can run one test group or the full test set.

In plain words
What is it for?
Use it for unit, database and queue integration, API contract, browser end-to-end, load, chaos, or fuzz testing. Contract tests check whether connected services still follow the same API agreement; fuzz testing sends unusual inputs to find weaknesses.
Why use it?
It helps check individual pieces, connections between services, complete user journeys, speed under load, and behavior during failures. This reduces the chance that changes break existing behavior.

Command

Install

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.

agentmods
npx agentmods add commands/saitarrun/devforge-ai/sdlc-test
Clone the repo
git clone --depth 1 https://github.com/saitarrun/Devforge-ai
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 614 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00614
Opus 5 $0.00015 $0.00307
Sonnet 5 $0.00006 $0.00123
Haiku 4.5 $0.00003 $0.00061

Measured 2d ago against content hash a7eb7c21b47f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sdlc-test 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.

commands/sdlc-test.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Enterprise Test Suite Generation & Execution Command

This command allows developers and agents to scaffold, generate, and run specialized multi-tier test suites across every layer of the application.

Usage

/sdlc-test --suite unit                  # Run fast unit test suite with coverage
/sdlc-test --suite integration           # Run Testcontainers database and queue integration tests
/sdlc-test --suite contract              # Validate Pact / OpenAPI consumer contracts
/sdlc-test --suite e2e                   # Execute Playwright browser workflows
/sdlc-test --suite perf                  # Run k6 load, spike, and latency benchmark tests
/sdlc-test --suite chaos                 # Execute fault injection and network latency tests
/sdlc-test --suite fuzz                  # Run property-based security fuzzing
/sdlc-test --suite all                   # Execute full enterprise verification matrix
/sdlc-test --suite perf --target claims  # Scaffold load test specifically for claims service

Process

  1. Test Matrix Resolution:
    • Identifies target layers (Database, HTTP API, Browser UI, Queue, or Distributed Cluster).
  2. Deterministic Harness Setup:
    • Spins up ephemeral test dependencies via Testcontainers or mock servers (MSW).
  3. Execution & Metric Assertion:
    • Evaluates test outcomes, code coverage (>80%), p95 latency thresholds, and circuit-breaker tripping.
  4. Comprehensive Reporting:
    • Emits structured pass/fail reports with trace artifacts, flamegraphs, and coverage heatmaps.

Output Format

### 🧪 Enterprise Test Matrix Execution Report

| Suite | Runner | Tests | Status | Key Metric / SLA |
|---|---|---|---|---|
| **Unit** | Vitest | 142 | ✅ Passed | 88.4% Branch Coverage |
| **Integration** | Testcontainers (Postgres + Redis) | 38 | ✅ Passed | 0 Stale Connections |
| **Contract** | Pact Broker | 12 | ✅ Passed | 100% Schema Parity |
| **E2E** | Playwright | 15 | ✅ Passed | Zero UI Regressions |
| **Load (Perf)** | k6 | 5,000 reqs | ✅ Passed | p95 Latency: 42ms (Budget: <100ms) |
| **Chaos** | Fault Injection | 4 Scenarios | ✅ Passed | DB Failover Recovered in 1.2s |
| **Fuzzing** | Fast-Check | 10,000 runs | ✅ Passed | 0 Uncaught Exceptions |

Read the full file on GitHub · 50 lines

Changes

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.

  1. 2d ago First seen · 50 lines · 31 tokens per session scan A a7eb7c21b47f

Subscribe to this mod's changes

sdlc-test is a command published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 31 tokens to every session and 614 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.