Rulesync is a command-line tool that generates configuration for different AI development tools from a shared set of rules. Developers use it to keep instructions, commands, MCP settings, ignore files, subagents, and skills consistent across coding agents. Catalogue skills support workflows built around Rulesync.
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 dyoshikawa/rulesync --skill draft-releasegit clone --depth 1 https://github.com/dyoshikawa/rulesyncWrote 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/dyoshikawa/rulesync/draft-release)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/draft-release"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/draft-release/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/dyoshikawa/rulesync/draft-release"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/draft-release.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.00011 | $0.00566 |
| Opus 5.5 | $0.00004 | $0.00226 |
| Sonnet 5.5 | $0.00002 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
draft-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 2d 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.
What it actually says
First, let's work on the following steps.
- Confirm that you are currently on the main branch and pull the latest changes. If not on main branch, switch to main branch.
- Compare code changes between the previous version tag and the latest commit to prepare the release description.
- Write in English.
- Do not include confidential information.
- Sections,
What's Changed,ContributorsandFull Changelogare needed. ./tmp/release-notes/*.mdwill be used as the release notes.
Then, from $ARGUMENTS, get the new version without v prefix, and assign it to $new_version. For example, if $ARGUMENTS is "v1.0.0", the new version is "1.0.0".
If $ARGUMENTS is empty, determine the new version automatically by performing the release-dry-run skill.
Let's resume the release process.
- Run
git pull. - Run
git checkout -b release/v${new_version}. - Update
getVersion()function to return the ${new_version} insrc/cli/program.ts, and runpnpm cicheck. If the checks fail, fix the code until pass. Then, executegit add,git commitandgit push. - Update the version with
pnpm version ${new_version} --no-git-tag-version. - Since
package.jsonwill be modified, executegit commitandgit push. - As a precaution, verify that
getVersion()insrc/cli/program.tsis updated to the ${new_version}. - Run
gh pr createto the main branch. - Create a draft release using
gh release create v${new_version} --draft --title v${new_version} --notes-file ./tmp/release-notes/*.mdcommand on thegithub.com/dyoshikawa/rulesyncrepository. This creates a draft release so that the publish-assets workflow can upload assets later.
Note: the Homebrew tap formula (Formula/rulesync.rb) is NOT updated here. It embeds sha256 checksums of the release binaries, which only exist after the release PR merges and the Publish Assets workflow uploads them. The goal-release skill performs that update as its post-merge step (regenerate with scripts/generate-homebrew-formula.ts from the release's SHA256SUMS and land it via an immediately merged PR). When releasing manually without the goal-release skill, run that step yourself after the assets are published.
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.
- 2d ago Changed 1de1241e2fb7
- 1mo ago First seen · 34 lines · 11 tokens per session scan A 621580bab37d
draft-release is a skill published in the GitHub repository dyoshikawa/rulesync (1,540 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 566 once invoked, about $0.0000 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
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
add-changelog-entry
Add a changelog entry to UNRELEASED.md.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.