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 ychampion/cskill-agents --skill legacy-wire-name-compat-translationgit clone --depth 1 https://github.com/ychampion/cskill-agentsWrote 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/ychampion/cskill-agents/legacy-wire-name-compat-translation)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/legacy-wire-name-compat-translation"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/legacy-wire-name-compat-translation/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/ychampion/cskill-agents/legacy-wire-name-compat-translation"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/legacy-wire-name-compat-translation.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.00033 | $0.00538 |
| Opus 5 | $0.00016 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
legacy-wire-name-compat-translation 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 7d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Legacy Wire Name Compat Translation
Domain: wire-compatibility Trigger: Apply when an internal tool, command, or capability identifier has been renamed, but existing SDK or UI consumers still depend on the old wire name and cannot safely break on a patch release. Source Pattern: Distilled from reviewed remote-control, bridge transport, and capability-advertising implementations.
Core Method
Keep the renamed identifier as the canonical internal name, then insert a narrow compatibility translator at the wire boundary that maps the new internal identifier back to the legacy external name before emitting payloads. Scope the translation to the specific renamed symbols that already escaped into client contracts, and keep it in place only until the explicitly planned version boundary where a breaking change is allowed. This preserves internal clarity and forward migration work without surprising patch-level consumers that still parse the legacy wire label.
Key Rules
- Translate at serialization time, not throughout business logic; the new identifier should remain canonical inside the codebase.
- Limit the mapping to the externally contracted names that actually changed, so unrelated identifiers keep flowing through untouched.
- Reuse one compatibility helper anywhere the wire payload is emitted, otherwise different event types or transports will drift and expose mixed names.
- Tie the shim to an explicit removal boundary such as the next minor or major release, and document that boundary next to the translator so the temporary contract does not become accidental forever behavior.
- Preserve stable wire names across both discovery and result surfaces when clients observe both; partial translation still breaks consumers that correlate the same capability across messages.
Example Application
If a product renames an internal tool from Task to Agent, keep Agent as the implementation name but translate it back to Task in init and result payloads until the next planned minor release. SDK clients that were built against the old wire contract continue to function, while the codebase and future migration work use the new canonical identifier internally.
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.
- 7d ago First seen · 30 lines · 33 tokens per session scan A 8181bf6cb79c
legacy-wire-name-compat-translation is a skill published in the GitHub repository ychampion/cskill-agents (36 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 538 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
grape
Use Grape MCP for Codex context continuity in coding repositories. Use when a task needs repeated-turn context, omitted context restore, stale-context checks, invalidation checks, or safe continuity across branch and dirty-worktree changes.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.
genie
Entry point for Genie operations — routes bug reports, questions, and operational commands, resumes existing lifecycle state, and orchestrates work that needs durable planning or coordination. Other ordinary requests bypass the lifecycle with a one-line notice unless the user asks for Genie.
wish
Convert an idea into a structured wish plan with scope, acceptance criteria, and execution groups for work.