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.
git clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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/saitarrun/devforge-ai/sdlc-review)<a href="https://agentmods.dev/commands/saitarrun/devforge-ai/sdlc-review"><img src="https://agentmods.dev/badge/commands/saitarrun/devforge-ai/sdlc-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/saitarrun/devforge-ai/sdlc-review"><img src="https://agentmods.dev/badge/commands/saitarrun/devforge-ai/sdlc-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.00030 | $0.00275 |
| Opus 5.5 | $0.00012 | $0.00110 |
| Sonnet 5.5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
sdlc-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 1mo 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
Code Review — Industry-Standard Review Style
Spawns agents in parallel: code-critic ×3 (compliance | bugs | history)
Outputs:
- Inline PR comments via
gh pr comment - Confidence-scored findings (only surface ≥80/100)
- Categorized as: blocking issues | important | nits
Process
- Backend Engineer Review: CLAUDE.md compliance, code patterns, SOLID principles
- Test Coverage Review: Missing tests, untested code paths
- Git History Review: Prior PRs, known issues, architectural decisions
Each reviewer confidence-filters (<80 is dropped), then findings are merged into one list.
Usage
/sdlc-review --pr 1 # Review PR #1
/sdlc-review --pr 1 --aspects all # All review aspects
Results
Comments are posted to the PR with:
- Blocking (red flag): Must fix before merge
- Important (yellow): Should fix before merge
- Nit (gray): Nice-to-have improvement
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.
- 1mo ago First seen · 37 lines · 30 tokens per session scan A d1bd0e198eaf
sdlc-review is a command published in the GitHub repository saitarrun/Devforge-ai (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 275 once invoked, about $0.0001 per session on Opus 5.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
review-feedback
Review a given code review markdown document, GitHub PR review, or inline feedback — corroborate each point against actual code, then implement valid changes.
address
Address code review feedback — corroborate, validate, and implement changes from a review's final.md.
sync-reviewers
Sync reviewer metadata from markdown files to reviewers-meta.json for the dashboard.
translate-review-to-single-human
Translate a multi-reviewer code review into a single human-voice GitHub PR comment.
create-reviewer
Create a new custom reviewer from a natural language description.
map
Generate a Code Review Map to help navigate large, complex changesets.