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-domain-driven-designgit 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-domain-driven-design)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-domain-driven-design"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-domain-driven-design/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-domain-driven-design"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-domain-driven-design.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.00071 | $0.01646 |
| Opus 5 | $0.00036 | $0.00823 |
| Sonnet 5 | $0.00014 | $0.00329 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
ralphctl-domain-driven-design 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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain-Driven Design
Adapted from wondelai/skills (MIT), itself distilling Eric Evans' Domain-Driven Design: Tackling Complexity in the Heart of Software (2003). Adapted for ralphctl's harness contract.
Framework for tackling software complexity by modeling code around the business domain. The greatest risk in software is not technical failure — it is building a model that does not reflect how the business actually works.
Core principle: the model is the code; the code is the model. When domain experts and developers speak the same language and that language is directly expressed in the codebase, complexity becomes manageable and the system evolves gracefully as the business changes.
When this applies
- Refine — name acceptance criteria in the domain's language; a criterion that needs technical jargon to state usually hides an unmodelled concept.
- Plan — draw task boundaries along context and aggregate boundaries, not along technical layers.
- Execute — apply the building blocks below when creating or renaming types, modules, and events.
1. Ubiquitous Language
A shared, rigorous language between developers and domain experts, used consistently in conversation, documentation, and code. Ambiguity is the root cause of most modeling failures — when a developer says "order" and an expert means "purchase request," bugs are inevitable.
- The language emerges from collaboration, not a glossary bolted on after the fact.
- If a concept is hard to name, the model is likely wrong — naming difficulty is a design signal.
- Technical jargon (
DataProcessorvs.ClaimAdjudicator) hides domain logic from the experts who could correct it. - Name classes and methods after domain concepts and verbs —
LoanApplication,policy.underwrite(), notRequestHandler,process(). - Organize modules by domain concept (
shipping/,billing/), not technical role (controllers/,services/). - In review, flag
Manager,Helper,Processor,Utilsas naming smells.
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.
- 9d ago First seen · 114 lines · 71 tokens per session scan A 18eb477741fd
ralphctl-domain-driven-design is a skill published in the GitHub repository lukas-grigis/ralphctl (23 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,646 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.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
My Skill
Content here.
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
atomic-verify
Evidence-before-claim gate. Auto-triggers when Claude is about to claim "done", "fixed", "passing", "complete", "ready to merge", "looks good", "should work", "should pass", "green", or any synonym. Iron rule: no completion claim without a fresh verification command run in this turn. Explicit invocation…