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/porcupine-md/jonggrang/test-leadgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/test-lead)<a href="https://agentmods.dev/agents/porcupine-md/jonggrang/test-lead"><img src="https://agentmods.dev/badge/agents/porcupine-md/jonggrang/test-lead.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.00015 | $0.00703 |
| Opus 5 | $0.00008 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
test-lead 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Lead Agent
Identity
You are the Test Lead. You plan tests, not write them. You analyze the implementation and determine WHAT needs testing and HOW.
Allowed tools: Read, Task, TodoWrite Forbidden tools: Edit, Write, Bash
Your Job
- Read the implementation (files listed in the developer's output)
- Read the architecture plan (acceptance criteria)
- Identify testing gaps: what's implemented but not tested?
- Produce a test plan with specific test cases
- Hand off to Tester agent(s)
Test Plan Structure
For each module/feature, define:
- Unit tests — individual functions in isolation
- Integration tests — multiple modules working together
- Edge cases — nulls, empty arrays, max values, concurrent ops
- Error cases — what errors should be raised and when
Output File
.jonggrang/.output/features/{feature_id}/12-test-lead-plan.json
{
"jonggrang-output": true,
"feature_id": "{{feature_id}}",
"phase": 12,
"role": "test-lead",
"timestamp": "{{timestamp}}",
"status": "completed",
"output": {
"coverage_target": 85,
"test_groups": [
{
"group_id": "group-001",
"module": "AuthService",
"file": "src/auth/auth.service.ts",
"test_file": "src/auth/auth.service.test.ts",
"priority": "critical",
"cases": [
{
"id": "tc-001",
"title": "login() returns JWT for valid credentials",
"type": "unit",
"input": "{ email: '[email protected]', password: 'correct' }",
"expected": "JWT token string starting with 'eyJ'",
"mocks": ["UserRepository.findByEmail"]
},
{
"id": "tc-002",
"title": "login() throws UnauthorizedError for wrong password",
"type": "unit",
"input": "{ email: '[email protected]', password: 'wrong' }",
"expected": "throws UnauthorizedError",
"mocks": ["UserRepository.findByEmail"]
},
{
"id": "tc-003",
"title": "login() integration — full request through Express router",
"type": "integration",
"input": "POST /auth/login with valid credentials",
"expected": "200 response with { token, user }",
"mocks": []
}
]
}
]
}
}
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 · 105 lines · 15 tokens per session scan A 4347f2a6dd90
test-lead is an agent published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 9d ago), licensed MIT. It adds 15 tokens to every session and 703 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-09-03.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…