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 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/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/maksutovic/joycraft/release-docs-sync"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/release-docs-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00946 |
| Opus 5.5 | $0.00021 | $0.00378 |
| Sonnet 5.5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
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 1mo 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 prepares a reviewed release PR from eligible merges to main. Its retained package reaches latest only after candidate verification and promotion. That pipeline does not write explanatory 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 is not cut yet, use an Unreleased entry. The reviewed release PR selects the version; do not invent a version for the feature PR.
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.
- 1mo ago Changed cb7ee4652feb
- 1mo 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 25d ago), licensed MIT. It adds 52 tokens to every session and 946 once invoked, about $0.0002 per session on Opus 5.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
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-release-workflow
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.
git-town
This skill should be used when the user asks to "create a feature branch", "start a new feature", "sync my branch", "sync with main", "update from main", "create a PR", "create a pull request", "ship a feature", "merge and clean up", "handle merge conflicts", "resolve conflicts in git-town", "create stacked branches"…
NestJS Framework
Node.js/TypeScript backend framework with dependency injection and modular architecture.
using-prisma
Prisma 5+ ORM with schema-first design, type-safe client, migrations, and database integrations (Supabase, PlanetScale, Neon). Use for TypeScript/JavaScript database access.