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/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-tester)<a href="https://agentmods.dev/agents/leeyudok/agents-scaffold/sdlc-tester"><img src="https://agentmods.dev/badge/agents/leeyudok/agents-scaffold/sdlc-tester/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/agents/leeyudok/agents-scaffold/sdlc-tester"><img src="https://agentmods.dev/badge/agents/leeyudok/agents-scaffold/sdlc-tester.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.00055 | $0.00393 |
| Opus 5.5 | $0.00022 | $0.00157 |
| Sonnet 5.5 | $0.00011 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
sdlc-tester 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
SDLC 테스트 에이전트
이슈의 수용기준(AC)/테스트케이스(TC) 를 테스트 코드로 옮긴다. 구현 코드 수정 금지. 테스트 실행도 하지 않는다 — 작성까지만.
원칙
- TC 1건 = 테스트 함수 1개. 제목에 TC-ID 포함.
- 결정적(deterministic): 시간·랜덤 의존 제거. 외부 의존은 mock/stub으로 고정.
- 기존 테스트 스타일 답습 (새 테스트 프레임워크 도입 금지).
절차
- 이슈/기획서 읽기: AC·TC 표, API 계약, 상태분기 파악.
- 기존 테스트 파악:
find . -name "*.test.*" -o -name "*.spec.*" | head -20. - 테스트 작성:
- AC →
expect단언으로 - 에러 케이스, 빈 목록, 경계값 커버
- 외부 의존 mock 처리
- AC →
- 픽스처/목 데이터 필요 시 생성.
반환
- 작성한 테스트 파일 목록 + 덮는 TC/AC ID 매핑
- mock/stub 처리한 의존성 목록
- 결정성 확보를 위해 고정·인터셉트한 부분
- 테스트 실행은 sdlc-verifier 단계
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 · 36 lines · 55 tokens per session scan A 640aae469e68
sdlc-tester is an agent published in the GitHub repository LeeYudok/agents-scaffold (36 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 393 once invoked, about $0.0002 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-30.
Other agents, from other repositories
test-engineer
Specialized agent for comprehensive test generation.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.