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/dyoshikawa/rulesync/goal-releasenpx skills add dyoshikawa/rulesync --skill goal-releasegit clone --depth 1 https://github.com/dyoshikawa/rulesyncWhat 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.00086 | $0.01920 |
| Opus 5 | $0.00043 | $0.00960 |
| Sonnet 5 | $0.00017 | $0.00384 |
| Haiku 4.5 | $0.00009 | $0.00192 |
Grade A, and why
goal-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 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal Release
new_version = the user's request
This skill drives a release all the way to merge. It uses the draft-release skill to
open the release pull request (and create the draft GitHub release), waits for
the PR's CI checks to pass, runs the merge-pr skill to merge it, and finally updates
the Homebrew tap formula once the release assets are built.
1. Draft the Release
Use the draft-release skill with new_version.
- If
new_versionis provided (e.g.v1.2.3or1.2.3), it must match the semver shape^v?\d+\.\d+\.\d+$— if it does not, stop and report instead of passing it on. Pass a valid value through unchanged; thedraft-releaseskill normalizes thevprefix itself. - If
new_versionis empty, pass no argument; thedraft-releaseskill determines the next version automatically via therelease-dry-runskill.
When the draft-release skill finishes, it has:
- created a
release/v<version>branch with the version-bump commits, - opened a pull request against
main, and - created a draft GitHub release
v<version>with the release notes.
If the draft-release skill failed partway (e.g. the PR exists but the draft release
was not created, or it stopped before opening the PR), stop here and report
the partial state to the user instead of continuing.
2. Resolve the Release PR
Use the PR number or URL that the draft-release skill's gh pr create printed in
Step 1 when available. Otherwise, identify the pull request from the current
release/v<version> branch:
gh pr view --json number,title,state,headRefName
Confirm that headRefName matches the release/v<version> branch created in
Step 1. This skill must only ever merge that release PR — if the resolved PR
is a different one, stop and report to the user instead of merging.
3. Wait for CI
Wait for the release PR's GitHub Actions checks to finish:
gh pr checks <pr_number> --watch
If the watch reports that no checks are registered yet, wait a moment and retry — checks can take a few seconds to appear right after the PR is opened.
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 · 179 lines · 86 tokens per session scan A 5f17d9ad0a54
goal-release is a skill published in the GitHub repository dyoshikawa/rulesync (1,373 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 1,920 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-30.
Other skills, from other repositories
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
repo-recap
Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
om-auto-update-changelog
Open Mercato releases must keep CHANGELOG.md, UPGRADENOTES.md, and version-specific downstream migration skills aligned. Apply this contract after the external skill resolves {version}, {date}, and the previous changelog release, but before it edits files or delegates to om-auto-create-pr.
document-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/AGENTS.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs".…