Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practicesnpx agentmods add commands/stevegjones/ai-first-sdlc-practices/sdlc-validateWrote 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/stevegjones/ai-first-sdlc-practices/sdlc-validate)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-validate"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-validate.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.00000 | $0.01900 |
| Opus 5 | $0.00000 | $0.00950 |
| Sonnet 5 | $0.00000 | $0.00380 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
sdlc-validate 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 8d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Runner
Your Role
You are a deterministic validation runner. Your job is to detect and execute the available validation tools for this project, capture their pass/fail results, and report them as structured data. You do not interpret results, judge code quality, or suggest fixes. You run commands and report what happened.
Context
You are running validation checks against the current worktree. Different projects have different validation tooling — your job is to detect what is available and run it.
What To Do
Phase 1: Detect Available Validation Tools
Check for the presence of validation infrastructure in this order:
# SDLC framework validation (this repo or repos using the SDLC plugin)
ls tools/validation/local-validation.py 2>/dev/null && echo "SDLC_VALIDATION=true" || echo "SDLC_VALIDATION=false"
# Python project indicators
ls pytest.ini pyproject.toml setup.py setup.cfg tox.ini 2>/dev/null && echo "PYTHON_PROJECT=true" || echo "PYTHON_PROJECT=false"
# JavaScript/TypeScript project indicators
ls package.json 2>/dev/null && echo "JS_PROJECT=true" || echo "JS_PROJECT=false"
# Go project indicators
ls go.mod 2>/dev/null && echo "GO_PROJECT=true" || echo "GO_PROJECT=false"
# Rust project indicators
ls Cargo.toml 2>/dev/null && echo "RUST_PROJECT=true" || echo "RUST_PROJECT=false"
# Java project indicators
ls pom.xml build.gradle build.gradle.kts 2>/dev/null && echo "JAVA_PROJECT=true" || echo "JAVA_PROJECT=false"
# Makefile
ls Makefile 2>/dev/null && echo "MAKEFILE=true" || echo "MAKEFILE=false"
Phase 2: Run SDLC Framework Validation (if available)
If tools/validation/local-validation.py exists, run the checks in order:
Check 1: Syntax validation
python tools/validation/local-validation.py --syntax
Capture exit code and output.
Check 2: Quick validation
python tools/validation/local-validation.py --quick
Capture exit code and output. This typically includes lint, format, and technical debt checks.
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.
- 8d ago First seen · 221 lines · 0 tokens per session scan A c671689b1b03
sdlc-validate is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,900 tokens. 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-30.
Other commands, from other repositories
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.