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 shimo4228/claude-harness --skill release-doigit clone --depth 1 https://github.com/shimo4228/claude-harnessWrote 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/shimo4228/claude-harness/release-doi)<a href="https://agentmods.dev/skills/shimo4228/claude-harness/release-doi"><img src="https://agentmods.dev/badge/skills/shimo4228/claude-harness/release-doi.svg" alt="Measured on agentmods" 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.00126 | $0.09225 |
| Opus 5 | $0.00063 | $0.04612 |
| Sonnet 5 | $0.00025 | $0.01845 |
| Haiku 4.5 | $0.00013 | $0.00923 |
Grade A, and why
release-doi scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://archive.softwareheritage.org/api/1/origin/save/git/url/https://github.com/<owner>/<repo>/" \ Copies of this mod
1 near-identical copy found in the catalogue:
- release-doi — 89% identical, 52 lines differ
How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-doi — DOI Release Runbook
Zenodo に DOI 登録された research repo のリリース手順。/release-doi で起動。
適用対象: AKC (agent-knowledge-cycle) / AAP (agent-attribution-practice) / contemplative-agent など、CITATION.cff を持ち GitHub release webhook で Zenodo が自動採番する shimo4228 系 repo。
When to use
- 直近の refactor / 新機能 / sunset ADR を Zenodo に新 version DOI として記録したい
- pyproject.toml / CITATION.cff / 多言語 README の version drift を解消したい
- glossary / llms.txt が code 実態とズレているのを release ゲートで揃えたい
Skip when:
- DOI 登録のない repo (Zenodo 連携していない) —
CITATION.cffの有無で判定 - バージョン bump の必要なし (typo fix 等の小修正で release を切らない)
- bug fix だけなら patch version で
/release-doiを起動、major refactor なら minor / breaking なら major
Pre-flight: 前提確認
# CITATION.cff があるか (= Zenodo 連携している repo か)
test -f CITATION.cff && echo "DOI repo" || echo "skip /release-doi"
# 直近 tag 以降の commit が空でないか (新規 repo なら tag なしで OK)
git log "$(git describe --tags --abbrev=0 2>/dev/null)..HEAD" --oneline | head
# Zenodo webhook が GitHub repo に登録されているか
gh api repos/<owner>/<repo>/hooks --jq '[.[] | select(.config.url | contains("zenodo"))] | length'
# → 0 が返ったら Zenodo opt-in 未実施。先に user に依頼する (下の "Zenodo opt-in" 参照)
# → 1 以上なら OK。webhook の active 状態も確認:
gh api repos/<owner>/<repo>/hooks --jq '.[] | select(.config.url | contains("zenodo")) | {active, url: .config.url[:50]}'
空なら release 不要。webhook 未登録なら opt-in 依頼後に再開。
Zenodo opt-in (新規 DOI repo の最初の release で必須)
Zenodo は GitHub repo ごとに opt-in 連携 が必要。toggle ON 前に作成された GitHub Release は Zenodo に届かず、後から ON にしても遡及的には拾われない (公式仕様)。新規 repo で初回 release を切る場合、必ず Phase 0 で opt-in を確認する。
ユーザー対応手順 (user が browser でやる):
! open https://zenodo.org/account/settings/github/— Zenodo の GitHub settings を開く- (必要なら) "Sync now" で repo 一覧を refresh
- 対象 repo を find → toggle を ON
- 完了確認
確認後、gh api repos/<owner>/<repo>/hooks で Zenodo webhook が登録されていることを再チェックしてから Phase 1 へ進む。
Phase 1: Verification baseline (read-only)
判断材料を ground truth として固定。実コマンド出力だけを信頼する (既存 doc の数値は drift しているので使わない)。
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.
- today Changed · -14 lines · -4 tokens per session b02816869e6c
- 2d ago Changed · -5 lines f4d6a3fb0202
- 7d ago First seen · 459 lines · 130 tokens per session scan A 494addd36050
release-doi is a skill published in the GitHub repository shimo4228/claude-harness (2 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 9,225 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-doi
A release checklist for research repositories that publish versions with Zenodo, a service that assigns permanent digital object identifiers (DOIs) to research outputs. It also records a Software Heritage identifier, which helps identify archived source code.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.