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/maksutovic/joycraft/release-docs-syncnpx skills add maksutovic/joycraft --skill release-docs-syncgit clone --depth 1 https://github.com/maksutovic/joycraftWrote 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/maksutovic/joycraft/release-docs-sync)<a href="https://agentmods.dev/skills/maksutovic/joycraft/release-docs-sync"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/release-docs-sync.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.00052 | $0.00939 |
| Opus 5 | $0.00026 | $0.00469 |
| Sonnet 5 | $0.00010 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
release-docs-sync 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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Docs Sync (Joycraft Maintainers)
This is a repo-local skill. It is not part of the Joycraft product and does not ship to npm — it lives in src/local-skills/ and exists only to maintain Joycraft's own documentation. Do not reference it from any skill under src/skills/.
Joycraft auto-publishes on every merge to main, patch-bumping when the version wasn't set manually. Nothing in that pipeline touches prose. Docs therefore drift silently: by 0.7.4 the CHANGELOG still stopped at 0.7.1, and AGENTS.md's architecture map never learned that src/copilot-skills/ existed.
Run this before opening a PR, while you still know what changed and why. After merge the version is already cut and the context is gone.
Step 1: Read the Branch
Get the actual diff against main — never guess from memory:
git diff main...HEAD --stat
git log main..HEAD --oneline
Read the diff for anything you are unsure about. What matters is not how many files moved but whether the contract with users changed.
Step 2: Decide What Each Doc Needs
Judge each independently. Most PRs need none of them, and saying so is a valid outcome — inventing an entry to look thorough is worse than skipping one.
CHANGELOG.md
The file states its own rule: it records "the releases that changed how Joycraft works," not every published version. Many patch versions exist between entries by design.
Add an entry when the branch changes what a user experiences:
- A new or removed skill, or a materially different workflow through an existing one
- A new harness, or a change to what
init/upgradewrites into a project - A changed default, a migration, or anything that alters an existing install on upgrade
- A fix for behavior users could have observed and built around
Skip when the change is internal: refactors, test-only work, generated-file regeneration, CI, or docs.
Match the existing format — ## <version> — <Title> (<date>), newest first, written as before → now → side-effects. Prose, not a bullet dump of commits. If the version isn't cut yet (it won't be — publish bumps on merge), use the version this PR will produce and say so in the PR body.
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.
- 3d ago First seen · 82 lines · 52 tokens per session scan A cd1c85612b75
release-docs-sync is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed 22d ago), licensed MIT. It adds 52 tokens to every session and 939 once invoked, about $0.0003 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
release
Cut a sim-use release end-to-end. Use when the user runs /release or asks to "ship a release", "publish a version", "cut a release", or "release to homebrew". Drives scripts/local-release.sh; never reimplement its build/sign/tarball logic.
bump-version-dev
Build a release-shaped sim-use binary and install it locally for testing. Use when the user runs /bump-version-dev or asks to "build a dev release", "test the release build locally", "install a release build for testing", or "prepare a release candidate without publishing". Builds APK + CLI, stages, ad-hoc signs, and…
prepare-release
End-to-end release automation — reads commits since last tag, infers semver bump, drafts changelog, creates release PR, merges it, waits for CI green, tags, and monitors the Docker build to completion. Use when the user says: prepare release, cut a release, bump version, create release PR, ship a new version, tag a…
release
Release a new version of BranchBox. Use when the user says "release", "new version", "cut a release", "publish release", or "tag version". Handles version bumping, changelog updates, quality checks, and GitHub release workflow.
git-conventional-commits
Prepare scoped conventional commits, tags, and release messages.
release-checklist
Prepare and validate application or framework releases.