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-source-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-source-driven-development)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-source-driven-development"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-source-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-source-driven-development"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-source-driven-development.svg" alt="Reviewed on agentmods" width="80" 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.00101 | $0.01230 |
| Opus 5.5 | $0.00040 | $0.00492 |
| Sonnet 5.5 | $0.00020 | $0.00246 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
ralphctl-source-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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source-Driven Development
Adapted from addyosmani/agent-skills — "Source-Driven Development" (MIT). Adapted for ralphctl's harness contract.
Version-sensitive code written from memory is a guess: training data goes stale, APIs get deprecated, recommended patterns move. Back every framework-specific decision with a source for the version this project resolves, and say plainly when you could not.
When not to use: the logic is version-independent (loops, data structures, renames, moving files), or the task does not touch a framework or library surface.
When this applies
- Plan — when a task depends on framework or library behaviour, name the resolved version and the documented pattern in the task's steps, so the implementing session does not have to guess.
- Execute — before writing version-sensitive code. When reviewing, a call that contradicts the installed version's API, or a deprecated pattern the installed version replaced, is a correctness finding.
The process
DETECT the version → LOOK IT UP (local first) → IMPLEMENT the documented pattern → RECORD the source
1. Detect the version
Read the dependency manifest for the stack (package.json, pyproject.toml, go.mod, Cargo.toml,
pom.xml, Gemfile, composer.json, …) and the lockfile for the version that actually resolves — a
manifest range is not a version. When the version cannot be determined, take the reading the lockfile or
installed copy most directly supports and state that assumption: record it in a note signal when the
prompt's output-contract section lists it; otherwise fold it into the required signal's own fields.
2. Look it up — local first
In order of preference:
- The installed dependency itself — its type declarations or headers, its source, the README and changelog shipped inside the dependency directory. Always readable, and always the right version.
- The project's existing usage of the same API — how this codebase already calls it.
- Official documentation for that version — the specific reference page, not a homepage — when the session can reach the network.
- The official changelog or migration guide for deprecations and replacements.
- Standards references for platform features (language specs, protocol RFCs, web standards).
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 First seen · 104 lines · 101 tokens per session scan A fc55cc223a4b
ralphctl-source-driven-development is a skill published in the GitHub repository lukas-grigis/ralphctl (24 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,230 once invoked, about $0.0004 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-10-18.
Other skills, from other repositories
study-plan
A long-term study planner that divides learning into stages and adapts the schedule using practice results. It can also plan focused practice sessions for a specific number of questions or flashcards.
outline-builder
A study aid that helps build an outline from a learner's notes, textbook excerpts, or an existing outline. It creates the structure and leaves gaps for the learner to fill rather than writing the lesson for them.
exam-forecast
An exam-pattern guide that compares several past papers from the same teacher or course. It identifies recurring topics, question formats, common traps, and changes over time, then estimates which areas may deserve more study.
flashcards
A lightweight flashcard and review method for learning facts and concepts in a conversation. It uses Leitner boxes, a simple system that shows cards at increasing intervals as they are remembered.
weak-point-drill
A targeted practice workflow that finds the topics a learner repeatedly gets wrong and gives those topics more questions. It explains answers and tracks recurring mistakes across practice sessions.
product-help
Answer questions about how to use octo, or diagnose something that isn't working, by reading the product documentation. Use when the user asks "how do I...", "what is...", "where is the docs for...", any usage/help question about octo itself, or reports a problem — "not working", "won't start", "error", "connection…