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 triage-issuesgit 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/triage-issues)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/triage-issues"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/triage-issues/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/triage-issues"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/triage-issues.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.00026 | $0.00856 |
| Opus 5.5 | $0.00010 | $0.00342 |
| Sonnet 5.5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
triage-issues 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 21d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Open Issues
Review all open GitHub issues that currently have no labels and apply the most appropriate labels based on their content.
Step 1: List Available Labels
Fetch the full list of labels defined in this repository so the triage stays within the known label set:
gh label list --limit 100
Treat this list as the authoritative vocabulary. Do not invent new labels.
Step 2: Find Unlabeled Open Issues
Fetch all open issues that have no labels attached:
gh issue list --state open --search "no:label" --limit 100 --json number,title,author,url
If the result is empty, report that nothing needs triage and stop.
Step 3: Gather Context per Issue
For each unlabeled issue, read the description and the discussion so the label choice is grounded in the actual content:
gh issue view <issue_number>
gh issue view <issue_number> --comments
Run these in parallel across issues where practical.
Step 4: Decide the Labels
For each issue, pick the labels that best describe it. Typical signals:
bug— something is broken or behaves incorrectly.enhancement— a new feature, new tool/feature support, or a capability request.documentation— docs, README, ordocs/**/*.mdchanges.refactoring— internal restructuring without behavior change.improvement— quality, DX, or polish work that isn't a bug or a new feature.question— the author is asking for clarification or usage help.duplicate— already tracked by another issue (link it in a comment if you apply this).invalid/wontfix— only if the issue itself states this or the content clearly indicates it; otherwise skip.good first issue— small, well-scoped, approachable for newcomers.help wanted— maintainer explicitly wants external contribution; do not apply speculatively.considering— proposals that are worth discussing but not yet accepted.high priority— explicit urgency signals (regression, blocking users, security). Be conservative.security— security-relevant reports or hardening work.codex— specific to the Codex CLI integration.maintainer-scrap— do NOT add this unless the issue body explicitly says so; it's reserved for maintainer-only scratch notes.
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.
- 21d ago Changed · +1 lines 94ee8a1bde35
- 1mo ago First seen · 89 lines · 26 tokens per session scan A f9bb5415d7d1
triage-issues is a skill published in the GitHub repository dyoshikawa/rulesync (1,535 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 856 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.
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.
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.
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.