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/jongwony/epistemic-protocols/releasenpx skills add jongwony/epistemic-protocols --skill releasegit clone --depth 1 https://github.com/jongwony/epistemic-protocolsWrote 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/jongwony/epistemic-protocols/release)<a href="https://agentmods.dev/skills/jongwony/epistemic-protocols/release"><img src="https://agentmods.dev/badge/skills/jongwony/epistemic-protocols/release.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 | $0.00014 | $0.02564 |
| Opus 5 | $0.00007 | $0.01282 |
| Sonnet 5 | $0.00003 | $0.00513 |
| Haiku 4.5 | $0.00001 | $0.00256 |
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 5d 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.
Release (project-local)
Creates a CalVer tagged release with a hand-written narrative prepended to the body CI generates via scripts/package.js. Overrides the global /release skill for this repo.
Purpose
- Push CalVer tag → CI (
release.yml) runsscripts/package.jsto build ZIPs + producedist/release-notes.md, thengh release create --draft --notes-fileattaches it - Prepend a hand-written narrative block to the script-generated body so the release surfaces "why this release matters" before the commit list
- Leave publish (draft → published) to the user for manual review
Preconditions
- Working tree clean, on
main(or user-specified branch) ghauthenticated with push access to the target remote (fork or upstream)- Node 22+ on PATH (packaging requires
zlib.crc32)
Flow
Phase 1: Tag decision
- Previous tag:
git describe --tags --abbrev=0(excludes drafts, gives last tagged commit) - Today: derive
YYYY.MM.DDfrom current date - Candidate tag:
v{YYYY.MM.DD}, orv{YYYY.MM.DD}.{N+1}if same-day tag exists - If latest tag is already today's and is Draft (not published), ask whether to re-tag (delete + recreate) or increment
.N
Phase 2: Tag push
git tag <tag>git push origin <tag>→ triggersrelease.yml
Phase 3: Wait for CI draft
- Poll
gh run list --workflow=release.yml --limit 1 --json status,conclusion,databaseIdevery 5s, max 12 attempts (60s total) - When
status=completedandconclusion=success, fetch draft:gh release view <tag> --json body,url - If still
in_progressafter 60s: surface run URL and ask user whether to keep waiting - If CI fails: surface logs via
gh run view <id> --log-failed, do not proceed to Phase 4. Remediation: fix the cause and retag with.Nincrement, or clean up the pushed tag withgit push origin :refs/tags/<tag>before retrying
Phase 4: Narrative drafting
Analyze commits since previous tag:
git log --oneline <prev-tag>..HEAD
Select 3-4 highest-impact changes. Prioritize:
- New skills or protocols (
feat:with newSKILL.md) - Architectural principles (
rules/,CLAUDE.md, axiom tier changes) - User-facing behavior changes
- Cross-cutting refactors that affect multiple protocols
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.
- 5d ago First seen · 161 lines · 14 tokens per session scan A 44c1844895ac
release is a skill published in the GitHub repository jongwony/epistemic-protocols (160 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 2,564 once invoked, about $0.0001 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
taiyi-integration
TaiyiForge 第9阶段 — 闭环归档,CHANGELOG.md。四端通用。.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
new
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
plugin-publish
发布 Zhin.js 插件到 npm 和 Zhin 插件市场。Use when asked to publish a plugin, prepare for release, check publish readiness, or submit to the Zhin plugin marketplace. 引导完成发布前检查、版本管理和提交流程。.