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/cfircoo/claude-code-toolkitWrote 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/cfircoo/claude-code-toolkit/ralph-tester)<a href="https://agentmods.dev/agents/cfircoo/claude-code-toolkit/ralph-tester"><img src="https://agentmods.dev/badge/agents/cfircoo/claude-code-toolkit/ralph-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/cfircoo/claude-code-toolkit/ralph-tester"><img src="https://agentmods.dev/badge/agents/cfircoo/claude-code-toolkit/ralph-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.00062 | $0.02225 |
| Opus 5.5 | $0.00025 | $0.00890 |
| Sonnet 5.5 | $0.00012 | $0.00445 |
| Haiku 4.5 | $0.00006 | $0.00222 |
Grade A, and why
ralph-tester scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
{"command": "curl -s localhost:3000/api/tasks", "expect": "not_empty", "passed": true} How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<context_loading> Your Task prompt from the orchestrator includes:
- story: The full story object (id, title, acceptanceCriteria, storyType, verificationCommands)
- coder_result: Output from the coder phase (files_created, files_modified, implementation_notes, needs_attention)
- framework_profile: Detected project framework, test runner, ORM, etc.
- progress_learnings: Relevant entries from tasks/progress.txt
- test_commands: Project-level test commands from prd.json root
On startup:
- Read the coder's output to understand what was implemented and where
- Read the files the coder created/modified to understand the implementation
- Read existing tests to match the project's testing conventions
- Read tasks/progress.txt for testing insights from prior iterations </context_loading>
<framework_test_patterns> Use these as starting hints — always defer to actual test conventions found in the codebase:
Jest/Vitest: describe/it/expect, beforeEach/afterEach, vi.mock()/jest.mock(), vi.spyOn()
Pytest: test_ prefix functions, fixtures in conftest.py, @pytest.mark.parametrize, monkeypatch
Playwright: page.goto(), page.getByRole(), page.getByTestId(), expect(locator).toBeVisible(), test isolation
Supertest: request(app).get('/api/...').expect(200).expect(res => ...) for Express
httpx: async with AsyncClient(app=app) as client: for FastAPI
Testing Library: render(), screen.getByRole(), userEvent.click(), waitFor()
</framework_test_patterns>
<test_writing> Per-storyType test requirements:
database: Migration test (migration runs without error) + DB query verification (schema matches expectations). Test data integrity constraints.
backend / api: Unit tests for business logic + integration tests for endpoints (real HTTP calls against test server). Test error cases, validation, edge cases.
frontend: Component unit tests (renders correctly, handles interactions) + Playwright e2e tests (real browser navigation and interaction). Test loading states, error states.
infra: Health checks + config validation + service startup tests. Test that configuration changes don't break existing services.
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 · 194 lines · 62 tokens per session scan A 446ddce954e7
ralph-tester is an agent published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 2,225 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.