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-deprecation-and-migrationgit 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-deprecation-and-migration)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-deprecation-and-migration"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-deprecation-and-migration/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-deprecation-and-migration"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-deprecation-and-migration.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.00103 | $0.01382 |
| Opus 5.5 | $0.00041 | $0.00553 |
| Sonnet 5.5 | $0.00021 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
ralphctl-deprecation-and-migration 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deprecation and Migration
Adapted from addyosmani/agent-skills — "Deprecation and Migration" (MIT). Adapted for ralphctl's harness contract.
Code is a liability, not an asset: every line needs tests, upgrades, and attention from anyone working nearby. Deprecation removes code that no longer earns its keep; migration moves its consumers safely to what replaces it. Most teams are good at adding things and bad at removing them — this skill is the removal half.
When this applies
- Plan — sequence the work so each step ships on its own: the replacement first, consumers next, removal last and alone. Give the removal task the verification criterion "no remaining consumers", and keep each data-shape phase below a separate task.
- Execute — implement one phase per task. Do not fold an additive step and its destructive follow-up into one change, and do not remove anything a consumer still reaches.
Before removing anything
Hyrum's law makes removal hard: consumers depend on behaviour the replacement may not reproduce — ordering, defaults, error text, side effects. Answer first:
- Does the old thing still provide something nothing else does? If so, keep it.
- Who consumes it? Search code, configuration, scripts, docs, and tests, including dynamic lookups by name. Consumers outside this repository may exist — say so rather than assume none.
- Does a replacement exist and cover every critical use? If not, build that first.
- What does each consumer's move cost, against the ongoing cost of keeping both?
The process
- Replacement first. It covers the critical cases and is proven, not just "theoretically better".
- Mark the old path deprecated with the project's own mechanism — a deprecation annotation, a runtime warning, a changelog entry — when it has one. Do not invent a new notice file.
- Migrate incrementally. One consumer or area per change: find its touchpoints, switch it, confirm behaviour matches with its tests, remove its reference to the old path. Whoever retires a thing migrates its consumers or ships a compatible shim — never leave them to discover the break.
- Remove only at zero. Once no consumer remains: the code, its tests, docs, configuration, and the deprecation markers themselves.
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 · 107 lines · 103 tokens per session scan A 61232546c610
ralphctl-deprecation-and-migration is a skill published in the GitHub repository lukas-grigis/ralphctl (24 stars, last pushed today), licensed MIT. It adds 103 tokens to every session and 1,382 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
save-learning
Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do X', 'from now on', 'never do Y', or gives any instruction they want persisted across sessions. Proactively suggest when the user states a preference, convention, or rule they clearly want followed in…
review
Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from git status, or to review a specific backlog task by id such as task-65 or TASK-65. Also trigger when the user says things like "review", "review current changes", "check…
web-access
A method for handling difficult web tasks across search, page fetching, and a real browser. It covers sites that need login sessions, dynamic pages, anti-bot handling, or exploration before their structure is understood.
skill-creator
A skill for creating or improving reusable instructions for an agent. It covers capturing the intended workflow, writing a draft, testing it, and refining its trigger description.
repo
Repository operating rules for verified Mythos edits.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.