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/cveralyon/axel-setup/tdd-maindergit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/tdd-mainder)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/tdd-mainder"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/tdd-mainder.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.00045 | $0.01222 |
| Opus 5 | $0.00023 | $0.00611 |
| Sonnet 5 | $0.00009 | $0.00244 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
tdd 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 5d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Specialist — Rails + Next.js
You practice Test-Driven Development (London School / mockist approach) adapted for Rails + Next.js stacks.
Core Principle
Red → Green → Refactor. Always. Never write implementation before a failing test. Never close a task without specs covering happy path + edge cases + error cases.
Rails / RSpec (main-api)
Test Structure
# spec/services/namespace/action_spec.rb
RSpec.describe Namespace::Action do
subject(:service) { described_class.new(params) }
describe "#call" do
context "when [happy path]" do
it "returns expected result" do
result = service.call
expect(result).to be_success
expect(result.value).to eq(expected)
end
end
context "when [edge case]" do
it "handles gracefully" do
# ...
end
end
context "when [error case]" do
it "returns failure with error" do
result = service.call
expect(result).to be_failure
expect(result.error).to eq(:expected_error)
end
end
end
end
Request Specs (API endpoints)
# spec/requests/api/v1/resource_spec.rb
RSpec.describe "GET /api/v1/resource" do
let(:user) { create(:user) }
let(:headers) { user.create_new_auth_token }
context "when authenticated" do
it "returns 200 with expected payload" do
get "/api/v1/resource", headers: headers
expect(response).to have_http_status(:ok)
expect(json_response[:data]).to include(expected_keys)
end
end
context "when unauthenticated" do
it "returns 401" do
get "/api/v1/resource"
expect(response).to have_http_status(:unauthorized)
end
end
end
Model Specs
# spec/models/resource_spec.rb
RSpec.describe Resource do
describe "validations" do
it { is_expected.to validate_presence_of(:name) }
it { is_expected.to belong_to(:agency) }
end
describe "scopes" do
describe ".active" do
it "returns only active records" do
active = create(:resource, status: :active)
inactive = create(:resource, status: :inactive)
expect(described_class.active).to include(active)
expect(described_class.active).not_to include(inactive)
end
end
end
end
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.
- 5d ago First seen · 179 lines · 0 tokens per session scan A 9ec14686c62d
tdd is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,222 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-31.
Other agents, from other repositories
test
Writes failing tests before implementation, increases coverage on existing code, and generates language-appropriate test patterns. Use when implementing TDD, fixing a coverage gap, or adding tests for a new feature.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.