ralphctl-test-driven-development

ralphctl-test-driven-development is a skill for Claude Code, Codex from lukas-grigis/ralphctl. It costs 72 tokens per session (3,079 once invoked), scanned A, original, MIT.

A test-first coding workflow called test-driven development, or TDD: write a failing test, make it pass with the smallest change, then clean up the code.

In plain words
What is it for?
Implementing logic changes, bug fixes, and other behaviour changes; it does not apply to documentation or configuration-only edits.
Why use it?
It turns the expected behaviour into a check and helps confirm that bug fixes actually reproduce and solve the problem.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/lukas-grigis/ralphctl/ralphctl-test-driven-development
Any agent
npx skills add lukas-grigis/ralphctl --skill ralphctl-test-driven-development
Clone the repo
git clone --depth 1 https://github.com/lukas-grigis/ralphctl

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ralphctl-test-driven-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-test-driven-development.svg)](https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-test-driven-development)
Your own site
<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-test-driven-development"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-test-driven-development.svg" alt="Measured on agentmods" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,079 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00072 $0.03079
Opus 5 $0.00036 $0.01540
Sonnet 5 $0.00014 $0.00616
Haiku 4.5 $0.00007 $0.00308

Measured 4d ago against content hash 481460a9bd54, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ralphctl-test-driven-development 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 4d 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.

src/integration/ai/skills/bundled/ralphctl-test-driven-development/SKILL.md · 344 lines

How it starts

The opening of the file, as written. The whole thing — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test-Driven Development

Concept from Addy Osmani — "Test-Driven Development" (agent-skills, MIT). Adapted for ralphctl's execute phase.

Write a failing test before writing the code that makes it pass. For bug fixes, reproduce the bug with a test before attempting a fix. Tests are proof — "seems right" is not done. A codebase with good tests is an AI agent's superpower; a codebase without tests is a liability.

When this applies

  • Execute — any new logic, bug fix, or behavioural change. Follow the RED→GREEN→REFACTOR cycle for each unit of work. Run the project's narrow check after each step; emit <task-complete> once the task's acceptance criteria are met. The harness runs the post-task verify gate — you do not own that verdict.

When NOT to use: Pure configuration changes, documentation updates, or static content changes with no behavioural impact.

The TDD Cycle

    RED                GREEN              REFACTOR
 Write a test    Write minimal code    Clean up the
 that fails  ──→  to make it pass  ──→  implementation  ──→  (repeat)
      │                  │                    │
      ▼                  ▼                    ▼
   Test FAILS        Test PASSES         Tests still PASS

Step 1: RED — Write a Failing Test

Write the test first. It must fail. A test that passes immediately proves nothing.

// RED: This test fails because createTask doesn't exist yet
describe('TaskService', () => {
  it('creates a task with title and default status', async () => {
    const task = await taskService.createTask({ title: 'Buy groceries' });

    expect(task.id).toBeDefined();
    expect(task.title).toBe('Buy groceries');
    expect(task.status).toBe('pending');
    expect(task.createdAt).toBeInstanceOf(Date);
  });
});

Step 2: GREEN — Make It Pass

Write the minimum code to make the test pass. Do not over-engineer:

// GREEN: Minimal implementation
export async function createTask(input: { title: string }): Promise<Task> {
  const task = {
    id: generateId(),
    title: input.title,
    status: 'pending' as const,
    createdAt: new Date(),
  };
  await db.tasks.insert(task);
  return task;
}

Read the full file on GitHub · 344 lines

Changes

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.

  1. 4d ago First seen · 344 lines · 72 tokens per session scan A 481460a9bd54

Subscribe to this mod's changes

ralphctl-test-driven-development is a skill published in the GitHub repository lukas-grigis/ralphctl (23 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 3,079 once invoked, about $0.0004 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.