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 prs-awaiting-authorgit 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/prs-awaiting-author)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/prs-awaiting-author"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/prs-awaiting-author/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/prs-awaiting-author"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/prs-awaiting-author.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.00053 | $0.00835 |
| Opus 5.5 | $0.00021 | $0.00334 |
| Sonnet 5.5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
prs-awaiting-author 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List PRs Awaiting Author Action
Identify open pull requests where the ball is in the author's court — the next action belongs to the PR author (fix CI, address review feedback, answer a question), not a maintainer.
Signals That the Ball Is on the Author's Side
- CI is failing or has not been made to pass (failing or stuck checks).
- The latest review is
CHANGES_REQUESTEDand the author has not pushed follow-up commits since. - There are review comments / inline threads the author has not yet replied to or resolved.
- A maintainer asked a question that is awaiting the author's reply.
- The PR is a draft (still work in progress on the author's side).
Exclude a PR when the next action clearly belongs to the maintainer (see the complementary prs-awaiting-maintainer skill): CI green, author has responded, and the PR is awaiting first review, re-review, or merge.
Step 1: List Open PRs
gh pr list --state open --limit 100 --json number,title,author,isDraft,createdAt,updatedAt,url,reviewDecision,reviewRequests
Include drafts here — a draft is, by definition, still on the author's side.
Step 2: Gather Per-PR Signals
For each PR, gather details (run in parallel across PRs where practical):
- CI status:
gh pr checks <number>— flag the PR if any check is failing. - Reviews and decision:
gh pr view <number> --json reviewDecision,reviews,latestReviews— flag if the decision isCHANGES_REQUESTED. - Discussion and who spoke last:
gh pr view <number> --comments, and if neededgh api repos/{owner}/{repo}/pulls/<number>/commentsfor inline review threads — flag if a maintainer's comment or question is the most recent and remains unanswered. - Commit timeline vs. last review time: to determine whether the author has pushed commits after a
CHANGES_REQUESTEDreview (if not, the ball is still with the author).
The maintainers for this repository are dyoshikawa and cm-dyoshikawa; use this login list as the primary way to tell the maintainer side from the author side. Note that gh pr view --json does not expose author_association — that field is only available per comment or review through gh api repos/{owner}/{repo}/pulls/<number>/comments and the reviews endpoint, where an author_association of OWNER, MEMBER, or COLLABORATOR indicates the maintainer side.
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 First seen · 58 lines · 53 tokens per session scan A b960e0afa282
prs-awaiting-author is a skill published in the GitHub repository dyoshikawa/rulesync (1,552 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 835 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
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.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
chinese-commit
A guide for writing Git commit messages in a shared format: an English change type followed by a short Chinese summary. Git commits are saved descriptions of changes to a codebase.
pr-description
A guide for writing Pull Request descriptions, which explain proposed code changes before teammates review them.
add-changelog-entry
Add a changelog entry to UNRELEASED.md.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.