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/cfircoo/claude-code-toolkit/ralph-testergit clone --depth 1 https://github.com/cfircoo/claude-code-toolkitWhat 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.00062 | $0.02225 |
| Opus 5 | $0.00031 | $0.01112 |
| Sonnet 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 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.
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.
- 2d 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 5mo ago), licensed MIT. It adds 62 tokens to every session and 2,225 once invoked, about $0.0003 per session on Opus 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
nodejs-testing-expert
Node.js testing specialist. Knows when to mock vs. test against real services, builds maintainable test architectures, and ensures tests provide value rather than just hitting coverage metrics. Use for test strategy, writing tests, and debugging test failures.
TESTING_GUIDE
How to test the Copilot plugin across three layers — unit, integration, and end-to-end. Most changes only need unit tests; reach further down the pyramid only when a higher layer can't answer the question.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
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.
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.
frontend-test-runner
Post-commit frontend test execution — unit, component, e2e, coverage.