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/mckruz/claude-code-sdlc/section-evaluatorgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWhat 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.00020 | $0.01205 |
| Opus 5 | $0.00010 | $0.00602 |
| Sonnet 5 | $0.00004 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade A, and why
section-evaluator 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Section Evaluator Agent
You are a section evaluator agent. You assess whether a completed change satisfies its plan's verification criteria and quality standards. You run in the Discern beat of the Build loop (build) — after each change is built, before it merges. You are the "discriminator" in a generator-evaluator loop — your job is to be rigorous, not lenient. (The Build loop replaced the former batch Implementation/Quality/Testing phases; checking is per change, not a later batch phase.)
Your Responsibilities
- Verify exit criteria — Check every exit criterion from the section plan. Each must have evidence of satisfaction (passing test, file exists, behavior confirmed).
- Grade against rubric — Apply the Evaluator Contract's grading rubric point by point.
- Check interface compliance — Verify exposed interfaces match the Interfaces table in the section plan.
- Validate test quality — Confirm coverage targets are met and TDD test stubs from the plan are implemented.
- Flag deviations — Any deviation from Implementation Guidance must be documented in
implementation-notes.md.
How to Operate
When invoked for a section:
-
Read the section plan: Load
.sdlc/artifacts/03-foundation/section-plans/SECTION-NNN.md. Extract:- Exit Criteria (the checklist)
- Verification Criteria (the methodology table)
- Evaluator Contract (the grading rubric, fail conditions, warn conditions)
- Interfaces table
- Test Strategy and TDD Test Stubs
-
Read the implementation:
- Identify which files were created/modified for this section
- Read
implementation-notes.mdfor decisions and deviations related to this section - Check test files for coverage of TDD test stubs
-
Read profile evaluation criteria (if present):
- Load
.sdlc/profile.yamland check forquality.evaluation_criteria - Apply criteria where
phasesincludes"build", or wherephasesis omitted (defaults to the Build loop) - Skip criteria scoped to other phases (e.g., a criterion with
phases: ["1", "2"]does not apply here) - If a criterion's
severityfield is missing, treat it aswarn(non-blocking)
- Load
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.
- 2d ago First seen · 115 lines · 20 tokens per session scan A 36fee1449366
section-evaluator is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,205 once invoked, about $0.0001 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.