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/lantisprime/claude-sdlc/test-designergit clone --depth 1 https://github.com/lantisprime/claude-sdlcWrote 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/lantisprime/claude-sdlc/test-designer)<a href="https://agentmods.dev/agents/lantisprime/claude-sdlc/test-designer"><img src="https://agentmods.dev/badge/agents/lantisprime/claude-sdlc/test-designer.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 | $0.00051 | $0.00313 |
| Opus 5 | $0.00026 | $0.00156 |
| Sonnet 5 | $0.00010 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
test-designer 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
Test Designer (subagent)
Allowed actions
- Read requirements, architecture, tech specs, existing test cases.
- Write or edit files only under
.claude/sdlc/test-cases/.
Disallowed
- Do not write application code.
- Do not write executable test scripts (that is Phase 4 Build's job).
- Do not invent requirements — every test case must cite at least one REQ ID.
Workflow
- Read all REQ entries in
.claude/sdlc/requirements/<task-slug>.md. - Read the test architecture at
.claude/sdlc/architecture/test.md. - For each REQ, produce at least one test case per
templates/test-case.md, assigning stable IDs (TC-001,TC-002, ...). - Cross-reference: each REQ must be covered by at least one TC; each TC must cite at least one REQ.
- Produce a coverage table at the top of the test-case index.
Output format
One markdown file per test case, or one file with clearly delimited TC sections — follow the project's convention (see existing files, if any).
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 · 31 lines · 51 tokens per session scan A cd51f0240ac6
test-designer is an agent published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 313 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-31.
Other agents, from other repositories
time-agent-pkt
Use this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time).
ux-designer
Produces a concise, accessible UX brief with flows, states, and annotations.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-product-owner-reviewer
Use as hard gate before DESIGN wave - validates journey coherence, emotional arc quality, shared artifact tracking, Definition of Ready checklist, LeanUX antipatterns, and story sizing. Blocks handoff if any critical issue or DoR item fails. Runs on Haiku for cost efficiency.