claudish-to-english is a Claude Code plugin that rewrites assistant messages into plain English for display, using a local or remote language model while preserving the original response and transcript. It is used by people who want easier-to-read Claude Code output, with an optional hook for simplifying Markdown files. The catalogue entries are the plugin's hooks, instruction, skill, command, and packaging.
Borrowing it
Nothing to install: this file belongs to gvzdv/claudish-to-english. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gvzdv/claudish-to-english/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/gvzdv/claudish-to-englishWrote 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/gvzdv/claudish-to-english/release)<a href="https://agentmods.dev/skills/gvzdv/claudish-to-english/release"><img src="https://agentmods.dev/badge/skills/gvzdv/claudish-to-english/release/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/gvzdv/claudish-to-english/release"><img src="https://agentmods.dev/badge/skills/gvzdv/claudish-to-english/release.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.00081 | $0.01569 |
| Opus 5 | $0.00041 | $0.00785 |
| Sonnet 5 | $0.00016 | $0.00314 |
| Haiku 4.5 | $0.00008 | $0.00157 |
Grade A, and why
release 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 12d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a release
Two phases. Phase 1 prepares the release and opens a PR. Then you STOP: the maintainer reviews and merges. Phase 2 tags and publishes, and can only run after the merge because the tag must point at the merge commit.
If $1 is a version (0.9.0, v0.9.0 — strip any leading v), use it. If not,
derive it and confirm before writing anything.
Phase 1 — prepare
1. Check the ground
git switch main && git pull --ff-only
git status --short
jq -r .version .claude-plugin/plugin.json
sed -n '1,40p' CHANGELOG.md
Stop and report if: the tree is dirty, main is not current, or CHANGELOG.md
has no ## [Unreleased] section with real entries under it. An empty Unreleased
section means there is nothing to release — say so rather than cutting an empty
version.
2. Pick the version
SemVer at 0.x, based on what is actually under ## [Unreleased]:
- MINOR (
0.8.0→0.9.0) if there is anything under### Added, or a### Changedentry that alters behaviour users rely on. New style preset, new provider, new env var. - PATCH (
0.8.0→0.8.1) only if every entry is under### Fixed.
Never hide a feature in a patch. State the version and the reason in one line before proceeding.
3. Edit the two files
Only these two carry a version. marketplace.json does not pin one — leave it.
CHANGELOG.md — three edits:
## [Unreleased]→## [<version>] - <today, YYYY-MM-DD>. Get today's date withdate +%F; do not guess it.- Add a comparison link ref in the block at the bottom, directly above the
previous version's line:
[<version>]: https://github.com/gvzdv/claudish-to-english/compare/v<previous>...v<version> - Repoint the Unreleased ref:
[Unreleased]: https://github.com/gvzdv/claudish-to-english/compare/v<version>...HEAD
Leave the [Unreleased] ref in place but do not re-add an empty
## [Unreleased] heading — this repo adds that heading only when there is
something to put under it.
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.
- 12d ago First seen · 161 lines · 81 tokens per session scan A e0fc4c19f8ce
release is a skill published in the GitHub repository gvzdv/claudish-to-english (2,566 stars, last pushed 14d ago), licensed MIT. It adds 81 tokens to every session and 1,569 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.