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 agentmods add skills/lukas-grigis/ralphctl/ralphctl-alignmentnpx skills add lukas-grigis/ralphctl --skill ralphctl-alignmentgit 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-alignment)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-alignment"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-alignment.svg" alt="Measured on agentmods" 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 | $0.00100 | $0.00720 |
| Opus 5 | $0.00050 | $0.00360 |
| Sonnet 5 | $0.00020 | $0.00144 |
| Haiku 4.5 | $0.00010 | $0.00072 |
Grade A, and why
ralphctl-alignment 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alignment
Concept from SPDD (Zhang & Xia, martinfowler.com) — "Alignment". Adapted for ralphctl's three phases.
The fastest way to ship the wrong thing is to start producing output before you have agreed on what is being asked. Alignment is the discipline of restating the input, surfacing assumptions, and naming the non-goals before the work begins. The cost of pausing to confirm is one round-trip; the cost of unwound output is the whole change.
When this applies
- Refine — refinement is itself an alignment exercise. Restate the ticket in one paragraph; list the assumptions you would have to make to implement it; agree before drafting acceptance criteria. A criterion built on a wrong premise is worse than a missing one.
- Plan — confirm the planner's read of the requirements before generating tasks. Repo selection, scope boundaries, and dependency assumptions all need to land before task decomposition starts.
- Execute — re-read the task spec's verification criteria before writing code. The contract is the
arbiter; if your read of it differs from what's written, surface the conflict in a
<note>rather than guessing.
What to do
- Restate the input. One paragraph. What you understood, in your own words. The user corrects the restatement before you spend their time on questions or output built on a wrong premise.
- List the assumptions. Every implicit choice you would have to make to produce output — preferred library, naming convention, error handling, scope boundary. Each one is a candidate for confirmation.
- Name the non-goals. What is out of scope is as load-bearing as what is in. Without explicit non-goals, scope creep is the default.
- Agree before producing output. Do not draft criteria, tasks, or code while the restatement and assumptions are still open. If the input cannot be restated, it is not yet refined enough to plan.
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.
- 4d ago First seen · 48 lines · 100 tokens per session scan A 45acb8442afe
ralphctl-alignment is a skill published in the GitHub repository lukas-grigis/ralphctl (23 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 720 once invoked, about $0.0005 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-copilot-provider
GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode.
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.