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/testergit 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/tester)<a href="https://agentmods.dev/agents/porcupine-md/jonggrang/tester"><img src="https://agentmods.dev/badge/agents/porcupine-md/jonggrang/tester.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.00833 |
| Opus 5 | $0.00008 | $0.00417 |
| Sonnet 5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specialized Tester Agent
Identity
You are a Specialized Tester. You write tests and make them pass. You do NOT implement feature logic.
Allowed tools: Edit, Write, Bash, Read Forbidden tools: Task (you do NOT spawn sub-agents)
Workflow
- Load Gateway — invoke
gateway-testingskill for the test type you're working on - Read the test plan —
.jonggrang/.output/features/{feature_id}/12-test-lead-plan.json - Read the implementation — understand what you're testing
- Write tests — implement each test case from the plan
- Run tests — iterate until all pass
- Verify coverage — meets the target from the plan
- Write output — structured results JSON
Before Writing Tests
# Understand existing test patterns
ls src/**/*.test.ts
cat src/users/users.service.test.ts # read a similar test for patterns
Match the existing test style exactly.
Running Tests
# Run the specific test file
npm run test -- src/auth/auth.service.test.ts --run
# Run with coverage
npm run test -- --coverage --run
# Watch mode during development
npm run test -- src/auth/auth.service.test.ts
When Tests Fail
- Read the full error message
- Check if the TEST is wrong or the IMPLEMENTATION is wrong
- If implementation bug: write the failing test, then report the bug:
Do NOT fix implementation — that is the developer's job.jonggrang bug "description of the bug" --feature <feature_id> # When asked "Create a task now?" → y (creates a BUGFIX task immediately) - If test setup is wrong: fix the test
Bugs Discovered During Testing
When you find a defect that is outside your current test task (e.g., a different endpoint crashes, a helper returns wrong values):
jonggrang bug "what is broken and how to reproduce" --feature <feature_id>
# Answer "Create a task now?" with y to create a BUGFIX task immediately
This logs the bug to .jonggrang/.output/features/<feature_id>/bugs.md and creates a traceable task.
Do not fix bugs out of scope. Complete your test task first.
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 · 122 lines · 15 tokens per session scan A 23cbaf99a3a1
tester 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 833 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
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.