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 dzhokhov/markdown-agent-vault-ru --skill release-rollbackgit clone --depth 1 https://github.com/dzhokhov/markdown-agent-vault-ruWrote 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/dzhokhov/markdown-agent-vault-ru/release-rollback)<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/release-rollback"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/release-rollback/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/dzhokhov/markdown-agent-vault-ru/release-rollback"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/release-rollback.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.00101 | $0.00480 |
| Opus 5 | $0.00051 | $0.00240 |
| Sonnet 5 | $0.00020 | $0.00096 |
| Haiku 4.5 | $0.00010 | $0.00048 |
Grade A, and why
release-rollback 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 8d 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.
What it actually says
Release Rollback
Назначение
Сделай релиз управляемым и обратимым: validate -> release decision -> rollback readiness.
Связанный контекст: LLM Rules.
Вход
RELEASE_CHECKLIST.mdCHANGELOG.md- текущий commit/branch/tag
- результаты
$test-gates
Mode A: Release Readiness
- Проверь
RELEASE_CHECKLIST.mdпо пунктам. - Убедись, что есть релизная версия (
vMAJOR.MINOR.PATCH) и запись вCHANGELOG.md. - Подтверди safe rollback point (последний стабильный tag/commit).
- Подготовь краткий release decision packet для владельца.
Mode B: Incident Rollback
- Freeze новые выкаты.
- Определи last known good version.
- Выбери путь отката (по убыванию стоимости):
- feature flag/config toggle off
git revertпроблемного изменения- откат на предыдущий стабильный tag
- Выполни post-rollback smoke.
- Зафиксируй, какой новый gate/тест нужен, чтобы не повторилось.
Жёсткие правила
- Не выпускать high-risk изменение без явного owner-решения.
- Не считать релиз готовым без rollback-пути.
- При конфликте между скоростью и безопасностью выбирай обратимость.
Выход
Release status: GREEN|YELLOW|REDRollback readiness: READY|NOT_READYOwner action:Release | Hold | RollbackNext safest step:1 конкретный шаг
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 49 lines · 101 tokens per session scan A ba2d1b6c477c
release-rollback is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed 2d ago), licensed MIT. It adds 101 tokens to every session and 480 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-31.
Other skills, from other repositories
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
sync-brain-starter
Sync reusable skills, configs, and templates from the private brain repo to the public brain-starter template repo. Use when you've updated a skill or config and want to push it to the open-source template.
github-deep-review
GitHub deep review: bugs, PRs, best fix, stale-or-real, read code first.
carpeos-release
Cut a CarpeOS public release with consistent SemVer, CHANGELOG, git tags, GitHub Releases, and npm publish for @innocarpe/carpeos. Use when the user asks to release, bump version, publish to npm, create a git tag, make a GitHub release, ship @innocarpe/carpeos, run scripts/release.mjs, or keep Claude Code / Codex CLI…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…