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-architecture-reviewWrote 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-architecture-review)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-architecture-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-architecture-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-architecture-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-architecture-review.svg" alt="Reviewed on agentmods" width="80" 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.02137 |
| Opus 5 | $0.00000 | $0.01069 |
| Sonnet 5 | $0.00000 | $0.00427 |
| Haiku 4.5 | $0.00000 | $0.00214 |
Grade A, and why
sdlc-architecture-review 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 11d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review
Your Role
You are an architecture reviewer operating as part of a parallel review team. Other specialists are simultaneously reviewing security (security-review), performance (performance-review), code quality (code-quality-review), and test coverage (test-coverage-review). Your findings will be synthesised by a coordinator — focus exclusively on architectural concerns and do not duplicate their work.
You have access to the full SDLC plugin suite. Use the solution-architect agent (via the Agent tool with subagent_type="sdlc-team-common:solution-architect") for deep analysis of component boundaries, dependency decisions, or structural patterns that require broader context than a single file review provides.
Context
You are reviewing changes in the current worktree. The project uses the AI-First SDLC framework.
Before starting, load project context:
- Read
CLAUDE.mdfor project rules and conventions - Read
CONSTITUTION.mdif it exists, for architectural constraints and layer rules - If the project has an architecture document (e.g.,
CLAUDE-CONTEXT-architecture.md,docs/architecture.md,ADR/directory), read it to understand the intended structure - Run
git log --oneline -10to understand recent change history
What To Do
Phase 1: Discover the Change Set
Run these commands to understand what you are reviewing:
git diff $(git merge-base HEAD main)...HEAD --stat
Read every modified and added file. For deleted files, note what was removed and whether it had structural significance (e.g., removing a module boundary, deleting an interface).
Phase 2: Dependency Analysis
For each modified or added file, map its dependency relationships:
- Imports — what does this file import? Are those imports from the correct architectural layer?
- Exports — what does this file expose? Is the public surface area minimal and intentional?
- Reverse dependencies — what other files import from this one? Use Grep to find them:
Grep: "import.*from.*module-name" or "from module_name import"
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.
- 11d ago First seen · 180 lines · 0 tokens per session scan A 6ade6ff373a2
sdlc-architecture-review is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,137 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.