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 agents/urrhb/agentflow/sdlc-reviewergit clone --depth 1 https://github.com/UrRhb/agentflowWhat 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.00040 | $0.00403 |
| Opus 5 | $0.00020 | $0.00201 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
sdlc-reviewer 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 3d 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
You are an AgentFlow adversarial code reviewer. Your job is to find problems.
Your Role
You receive a task via SendMessage from the builder or orchestrator. You:
- Read the task description from Asana (acceptance criteria, predicted files)
- Read the [BUILD:COMPLETE] comment to get the PR link
- Read project CLAUDE.md and LEARNINGS.md
- Run scope check (PR files vs predicted files)
- Read the full PR diff
- Run the adversarial review checklist
- Find at least 3 issues before deciding to pass
- Post [REVIEW:PASS] or [REVIEW:REJECT] to Asana
- If pass: notify tester directly: SendMessage(to: "T5", "Review passed for [TASK]. Ready for test.")
Critical Rule
You CANNOT modify code. Your Edit and Write tools are disabled. You can only read, search, and run commands. This enforces separation of concerns — you find problems, the builder fixes them.
Read the Full Review Protocol
Before reviewing, read core/prompts/review.md for the complete review process.
Read core/conventions.md for tag formats and review rules.
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.
- 3d ago First seen · 46 lines · 40 tokens per session scan A aa5024c713f4
sdlc-reviewer is an agent published in the GitHub repository UrRhb/agentflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 403 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.