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 skills add igmarin/rails-agent-skills --skill tddgit clone --depth 1 https://github.com/igmarin/rails-agent-skillsWrote 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/skills/igmarin/rails-agent-skills/tdd)<a href="https://agentmods.dev/skills/igmarin/rails-agent-skills/tdd"><img src="https://agentmods.dev/badge/skills/igmarin/rails-agent-skills/tdd/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/skills/igmarin/rails-agent-skills/tdd"><img src="https://agentmods.dev/badge/skills/igmarin/rails-agent-skills/tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01271 |
| Opus 5 | $0.00020 | $0.00635 |
| Sonnet 5 | $0.00008 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
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 10d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Persona
Agent Phases
Phase 1: Context & Test Design
- load-context: Load schema, routes, and patterns.
- plan-tests: Choose the best first failing spec.
- write-tests: Write test and verify failure.
HARD GATE — tdd-process (from ruby-core-skills)
- Test EXISTS and is RUN.
- FAILS for correct reason (e.g.,
undefined method 'full_name'). - If FAIL is incorrect (syntax, config), return to
write-tests.
Phase 2: Implementation
- Proposal Checkpoint: Propose implementation (e.g., "Concatenate first + last name").
- User Approval: Wait for explicit confirmation.
- Minimal Implement: Smallest change to pass test.
- Verify PASS:
bundle exec rspec spec/path/to/spec.rb.
If test does not pass, fix minimal changes and re-verify.
Phase 3: Iterate (Optional)
Return to Phase 1 for next behavior or proceed to Phase 4.
Phase 4: Finish
- Quality Check:
bundle exec rubocop && bundle exec brakeman && bundle exec rspec. - write-yard-docs (from ruby-core-skills): Document public Ruby API.
- code-review: Self-review PR diff.
- Open PR: Feature complete.
Concrete Example
Abbreviated walkthrough for adding a full_name method to a User model. For the full end-to-end example, see assets/example.md.
Step 1 — Write the failing spec (spec/models/user_spec.rb):
RSpec.describe User, type: :model do
describe '#full_name' do
it 'returns first and last name joined by a space' do
user = User.new(first_name: 'Jane', last_name: 'Doe')
expect(user.full_name).to eq('Jane Doe')
end
end
end
Run: bundle exec rspec spec/models/user_spec.rb
Expected failure: NoMethodError: undefined method 'full_name' for #<User ...> ✅
Step 2 — Propose & confirm
Proposal: Add
def full_name = "#{first_name} #{last_name}"toapp/models/user.rb. Proceed?
Step 3 — Minimal implementation (app/models/user.rb):
def full_name
"#{first_name} #{last_name}"
end
Run: bundle exec rspec spec/models/user_spec.rb → 1 example, 0 failures ✅
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 130 lines · 40 tokens per session scan A 259d8ec830b1
tdd is a skill published in the GitHub repository igmarin/rails-agent-skills (25 stars, last pushed 19d ago), licensed MIT. It adds 40 tokens to every session and 1,271 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 skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.