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 merge-prgit 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/merge-pr)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/merge-pr"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/merge-pr/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/merge-pr"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/merge-pr.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.00013 | $0.00659 |
| Opus 5.5 | $0.00005 | $0.00264 |
| Sonnet 5.5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
merge-pr 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 20d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Pull Request
Merge a pull request using gh pr merge --admin.
Input
the user's request
Step 1: Determine the Target PR
Parse the user's request to identify the PR to merge:
Case A: PR number or URL is provided
- Extract the PR number from the argument
- Examples:
123,#123,https://github.com/owner/repo/pull/123
Case B: No argument provided
- Get the PR associated with the current branch:
gh pr view --json number,title,state
Case C: Unable to determine the PR
If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), ask the user to specify which PR to merge.
Step 2: Verify the PR
Before merging, confirm the PR details:
gh pr view <pr_number> --json number,title,state,mergeable,author,baseRefName,headRefName
Check:
- The PR state is
OPEN - Display the PR title and number to the user (for visibility; do not wait for a reply)
If the PR is not open or not mergeable, inform the user and stop.
Step 3: Check GitHub Actions Workflow Status
Verify that all CI checks have passed before merging:
gh pr checks <pr_number>
Check:
- All workflow checks show
passstatus - No checks are
pendingorfail
If checks are still running, do not ask — wait for them with
gh pr checks <pr_number> --watch and merge once they all pass.
If any check has failed, inform the user and ask whether to:
- Investigate failed checks before merging
- Proceed with merge anyway (using
--adminwill bypass required checks)
Step 4: Merge the PR
Execute the merge command:
gh pr merge <pr_number> --admin --merge
Important: Only merge ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to merge.
Step 5: Comment on the PR
After the merge succeeds, leave a thank-you comment mentioning the PR author:
gh pr comment <pr_number> --body "@<author_login> Thank you!"
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.
- 20d ago Changed · +2 lines b31e0d303e2d
- 1mo ago First seen · 108 lines · 13 tokens per session scan A 3702d9b84b0d
merge-pr is a skill published in the GitHub repository dyoshikawa/rulesync (1,534 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 659 once invoked, about $0.0001 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.