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 post-issue-commentgit 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/post-issue-comment)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/post-issue-comment"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/post-issue-comment/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/post-issue-comment"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/post-issue-comment.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.00031 | $0.00491 |
| Opus 5.5 | $0.00012 | $0.00196 |
| Sonnet 5.5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
post-issue-comment 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.
What it actually says
arguments = the user's request
Parse arguments as:
target_issue: the issue number (or URL) to reply tointent: the gist of the reply the user wants to post (what to say, the stance to take, the points to cover)
If target_issue is not provided, ask the user which issue to comment on.
If intent is not provided, ask the user what the reply should convey.
Step 1: Gather Issue Context
Run the following in parallel:
- Get the issue description and metadata:
gh issue view <issue_number> - Get the issue comments:
gh issue view <issue_number> --comments
If the issue references related pull requests, commits, or files that are needed to craft an informed reply, gather that context as well.
Step 2: Draft the Reply
Based on the issue content and the user's intent, draft a reply comment.
- Ground the reply in the actual discussion — address the latest comment or the original issue as appropriate.
- Reflect the user's
intentfaithfully; do not add positions the user did not ask for. - If relevant context is missing or a decision cannot be made without more information, say so in the reply rather than guessing.
Step 3: Post the Comment
Post the drafted reply using:
gh issue comment <issue_number> --body "<reply body>"
Writing Style
Write in English only.
Style guidelines — write like a human teammate, not a bot:
- Use plain paragraphs. Avoid headings (
##), horizontal rules (---), and excessive bullet lists. - Keep it conversational and direct. Say what matters, skip the filler.
- Do not use phrases like "Great point!" or "Thanks for raising this!" unless you genuinely mean it and have nothing else to add.
- Be honest. If you disagree or see an issue, say so clearly but respectfully.
- Short is fine. A two-sentence comment is better than a five-paragraph essay with no substance.
Step 4: Report
Output the issue number and a brief summary of the comment that was posted.
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 · 60 lines · 31 tokens per session scan A 859020fd4c08
post-issue-comment is a skill published in the GitHub repository dyoshikawa/rulesync (1,530 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 491 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
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.