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 lukas-grigis/ralphctl --skill ralphctl-test-driven-developmentgit clone --depth 1 https://github.com/lukas-grigis/ralphctlWrote 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/lukas-grigis/ralphctl/ralphctl-test-driven-development)<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/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/lukas-grigis/ralphctl/ralphctl-test-driven-development"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-test-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 297 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 301 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 308 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00082 | $0.03558 |
| Opus 5.5 | $0.00033 | $0.01423 |
| Sonnet 5.5 | $0.00016 | $0.00712 |
| Haiku 4.5 | $0.00008 | $0.00356 |
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 yesterday.
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 — 372 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), with the tautological-assertion anti-pattern drawn from mattpocock/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; signal the work complete once the task's
acceptance criteria are met (generator role: a
task-completesignal — the evaluator's contract has notask-completeschema). 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.
Discover the Stack First
The TDD cycle is universal; the commands are not. Before writing the first test, find out how this repository tests, and use its commands for every RED, GREEN, and narrow-check step:
- Commands the harness hands you — the prompt's project-tooling or check-gate section, when present, is the authoritative source; prefer it over anything you infer.
- Language and build system — the dependency manifest or build file (
package.json,pom.xml/build.gradle,pyproject.toml,go.mod,Cargo.toml,Gemfile, aMakefile). - Checked-in wrappers — prefer a repo wrapper or script (
./gradlew,./mvnw, aMakefiletarget) over a globally installed tool. - Test framework and configuration — and how it runs a single focused test versus the full suite.
- Existing conventions — where tests live, how files are named, what patterns neighbouring tests follow.
- Documented commands — the project's AI context file, README, CONTRIBUTING, and CI workflows show the commands that actually gate merges.
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.
- yesterday Changed · +4 lines 0c21c7daddb1
- 6d ago Changed · +23 lines · +10 tokens per session a213767f0e58
- 1mo ago Changed · +1 lines 09d48414ae6e
- 1mo ago Changed ad9b2a4d71af
- 1mo ago First seen · 344 lines · 72 tokens per session scan A 481460a9bd54
ralphctl-test-driven-development is a skill published in the GitHub repository lukas-grigis/ralphctl (24 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 3,558 once invoked, about $0.0003 per session on Opus 5.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
implement
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a state file so work survives session restarts. Use when the user has a tech design (doc or settled conversation) and says…
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
implement-is-odd
Implement isOdd following test-driven development.
tdd
Discipline skill — TDD red-green-refactor cycle. Use when implementing any feature or bugfix, before writing implementation code.
tdd
A test-first coding workflow based on the red–green–refactor cycle: write a failing test, make it pass with the smallest change, then clean up the code.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.