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/nikitacodesave/claude-code-harness/releasenpx skills add nikitaCodeSave/claude-code-harness --skill releasegit clone --depth 1 https://github.com/nikitaCodeSave/claude-code-harnessWhat 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.00076 | $0.03002 |
| Opus 5 | $0.00038 | $0.01501 |
| Sonnet 5 | $0.00015 | $0.00600 |
| Haiku 4.5 | $0.00008 | $0.00300 |
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 2d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Релиз / обновление репозитория claude-code-harness
Этот репозиторий — source of truth публичного плагина. Консюмеры устанавливают из
origin/main через /plugin update. Отсюда два жёстких факта, которые формируют весь ритуал:
- Версия в
plugin.json— это update cache key. Правка shipped-поверхности БЕЗ бампа версии доставляет подписчикам ничего (см.native-capabilities.md§Plugins). Значит любое изменение подplugins/**обязано пройти через релиз с бампом. - Релиз существует только когда запушен (коммит + тег + push в origin). Незапушенный
релиз — это анонс в devlog без поставки. Три прошлых релиза сломались именно тут
(desync версий, стампы на несуществующих версиях, «зарелизил в devlog, но не запушил») —
ради этого и написан
scripts/release.sh.
Не переизобретай механику: plugins/harness/scripts/release.sh уже бампит обе версии,
стережёт drift и стейджит поверхность. Этот скилл — рунбук поверх него: решение + пред-шаги +
финиш + верификация, то, что скрипт намеренно не делает.
Шаг 0. Развилка — нужен ли тег?
Посмотри git status / git diff --stat. Задевает ли изменение shipped-поверхность?
- Shipped-поверхность =
plugins/**·README.md·CHANGELOG.md·.claude-plugin/marketplace.json. → Путь B (Релиз): version bump + тег. - Только dev-harness =
.claude/**(CLAUDE.md, этот скилл, devlog-правка) ·.gitignore·.gitattributes·LICENSE. → Путь A (Dev-harness commit): обычный commit + push, без бампа, без тега.
Пограничный случай: изменение задевает и то, и другое (например, правка reference + правка CLAUDE.md). Тогда это Путь B — раз shipped-поверхность затронута, нужен релиз; dev-harness-файлы просто едут в том же коммите.
Ты работаешь в main (консюмеры ставят из origin/main) — релизы идут прямо в main, это
установившийся поток. Убедись, что ты на main и что пользователь действительно просил
опубликовать, прежде чем пушить.
Путь A — dev-harness фикс (без тега)
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.
- 2d ago First seen · 189 lines · 76 tokens per session scan A f04eb08b7e10
release is a skill published in the GitHub repository nikitaCodeSave/claude-code-harness (5 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 3,002 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.