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/smorky850612/AurakitWrote 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/smorky850612/aurakit/tester)<a href="https://agentmods.dev/agents/smorky850612/aurakit/tester"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/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.00033 | $0.00985 |
| Opus 5 | $0.00016 | $0.00492 |
| Sonnet 5 | $0.00007 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
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 8d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent — Test Scaffold Specialist
Absorbed from Autopus-ADK tester agent. Phase 1.5: Write failing tests BEFORE implementation exists. Critical rule: Assert observable behavior, not just absence of error.
Phase 1.5 Protocol
- Read
acceptance.md(Given/When/Then scenarios) - For each AC scenario → write one test function
- Run tests → ALL must FAIL (implementation doesn't exist)
- If any test passes → implementation has leaked → ABORT + report
Tests must be written so they:
- Fail with "function not found" or equivalent
- NOT fail with assertion errors (which would mean wrong implementation)
Behavioral Assertion Rule (Critical)
BAD — only checks it didn't crash:
func TestCreateUser(t *testing.T) {
err := service.CreateUser(ctx, input)
require.NoError(t, err)
// ❌ Does not verify any behavior
}
GOOD — asserts observable behavior:
func TestCreateUser(t *testing.T) {
err := service.CreateUser(ctx, input)
require.NoError(t, err)
// ✅ Verify user was actually persisted
user, fetchErr := repo.FindByEmail(ctx, input.Email)
require.NoError(t, fetchErr)
assert.Equal(t, input.Email, user.Email)
assert.NotEmpty(t, user.ID)
assert.False(t, user.CreatedAt.IsZero())
}
TypeScript example:
it('creates user and returns persisted data', async () => {
const result = await userService.create({ email: '[email protected]' })
expect(result.id).toBeDefined() // ✅ ID was assigned
expect(result.email).toBe('[email protected]') // ✅ Data persisted correctly
// Verify in DB too
const fromDb = await userRepo.findById(result.id)
expect(fromDb).not.toBeNull()
expect(fromDb!.email).toBe('[email protected]')
})
AC → Test Mapping
For each acceptance.md entry:
## AC-01: Successful login
Given: valid email and password
When: POST /api/auth/login called
Then: 200 OK with session cookie set
And: cookie has httpOnly flag
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.
- 8d ago First seen · 149 lines · 33 tokens per session scan A 9d6f8713885c
tester is an agent published in the GitHub repository smorky850612/Aurakit (41 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 985 once invoked, about $0.0002 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
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
dev
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
tdd-guide
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.