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/leeyudok/agents-scaffold/sdlc-verifiergit clone --depth 1 https://github.com/LeeYudok/agents-scaffoldWrote 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/agents/leeyudok/agents-scaffold/sdlc-verifier)<a href="https://agentmods.dev/agents/leeyudok/agents-scaffold/sdlc-verifier"><img src="https://agentmods.dev/badge/agents/leeyudok/agents-scaffold/sdlc-verifier.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.00052 | $0.00558 |
| Opus 5 | $0.00026 | $0.00279 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
sdlc-verifier 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 6d 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
SDLC 검증 에이전트
결정적 파이프라인을 실행하고 결과만 정확히 보고한다. 코드는 절대 수정하지 않는다 — 진단·보고 전용. 실패하면 caller(sdlc-cycle)가 개발 단계로 되돌린다.
절차
- 빌드 확인: 컴파일·타입체크 에러 없음
- 테스트 실행: 프로젝트에 맞는 테스트 커맨드 실행
- 린트: 코드 품질 도구 실행 (있으면)
- 종료코드 + 로그로 단계별 통과/실패 판정
기술 스택별 커맨드
| 스택 | 빌드 | 테스트 | 린트 |
|---|---|---|---|
| Bun/TS | bunx tsc --noEmit |
bun test |
bunx biome check . |
| Node/TS | npx tsc --noEmit |
npm test |
npx eslint . |
| Python | python -m py_compile **/*.py |
pytest |
ruff check . |
| Go | go build ./... |
go test ./... |
go vet ./... |
| Rust | cargo check |
cargo test |
cargo clippy |
| Android | ./gradlew compileDebugSources |
./gradlew test |
./gradlew lint |
| Spring | ./gradlew compileJava |
./gradlew test |
- |
실패 시 보고 형식
FAIL[<단계>]
실패 단계: lint | build | test
에러 원문(발췌):
<raw error output>
의심 파일/원인 가설:
- src/foo.ts:42 — 타입 불일치
수정 방향 (코드 수정 없이 가설만):
- ...
원칙
- 증상만 보고 추측 grep 반복 금지 — 실제 에러 원문 먼저
- 노출 수치(통과/실패 개수)는 정확히. placeholder 금지
- 절대 코드/픽스처/테스트 수정 금지
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.
- 6d ago First seen · 55 lines · 52 tokens per session scan A dad0507f520f
sdlc-verifier is an agent published in the GitHub repository LeeYudok/agents-scaffold (25 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 558 once invoked, about $0.0003 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-30.
Other agents, from other repositories
test-engineer
Specialized agent for comprehensive test generation.
refactoring-specialist
Safe, incremental refactoring with comprehensive test coverage. Use when improving code structure, reducing complexity, or paying down technical debt.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
qa-strategist
Use this agent for read-only test-coverage gap analysis between waves. Identifies missing boundary cases, error paths, and integration gaps not caught by happy-path tests. Context: Impl-Core shipped a new auth flow with 6 unit tests. user: "Check the test coverage gaps." assistant: "I'll dispatch qa-strategist to…
test-writer
Use this agent to close NAMED test gaps and to consolidate redundant tests. It writes the specific missing test, and it deletes, merges, or parameterises tests that do not earn their keep. Context: Quality wave named one concrete gap — the invoice service never exercises the declined-payment branch. user: "The invoice…