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-issue-to-external-repositorygit 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-issue-to-external-repository)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/draft-issue-to-external-repository"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/draft-issue-to-external-repository/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-issue-to-external-repository"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/draft-issue-to-external-repository.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 101 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 52 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00079 | $0.01772 |
| Opus 5.5 | $0.00032 | $0.00709 |
| Sonnet 5.5 | $0.00016 | $0.00354 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
draft-issue-to-external-repository scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- If the proposal includes popularity / adoption claims, verify the numbers before writing them down. For npm downloads: `curl -s "https://api.npmjs.org/downloads/point/<start>:<end>/<package>"`. For stars/forks: `gh rep How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
arguments = the user's request
Parse arguments as:
target_repo: the target repository inowner/repoform (or a URL)intent: the rough idea the user wants to propose (may be vague — this skill is designed to sharpen it)
If target_repo is not provided, ask the user which repository to file against.
If intent is not provided, ask the user what they want to propose.
This skill is for proposing a change to a repository we do not own. When the target is a repo under the user's own owner, prefer create-issue or create-issue-with-websearch instead.
Step 1: Inspect the Target Repository
Before drafting anything, understand the target repo's conventions. Run in parallel:
gh repo view <owner/repo> --json description,url,defaultBranchRef,primaryLanguage,latestReleasegh issue list --repo <owner/repo> --limit 20 --state all --json number,title,labels,state— read recent titles to learn the house style (prefix tags like[FEATURE], casing, length).gh api repos/<owner/repo>/contents/.github/ISSUE_TEMPLATE— list templates. If a feature-request template exists, fetch it withgh apior a raw URL and note the required sections plus any auto-applied title prefix / labels.gh label list --repo <owner/repo>— note which labels exist (do not invent labels later).- Optionally fetch
CONTRIBUTING.md/CODE_OF_CONDUCT.mdif present to catch any issue-filing rules.
If no issue template exists, plan to use a light structure (Problem / Proposal / Alternatives / Additional context) that mirrors common feature-request templates.
Step 2: Research the Topic
Ground the proposal in primary sources before writing anything opinionated.
- Use
WebSearch/WebFetchfor official docs of the target project, release notes, and any pre-existing discussion (open/closed issues, PRs, RFCs). - Use the deepwiki MCP (
mcp__deepwiki__ask_question,mcp__deepwiki__read_wiki_contents) against the target repo for structural questions — it is often faster and more definitive than grepping manually. - For deep or multi-angle investigation, delegate to a subagent (
Agentwithsubagent_type: "general-purpose") with a self-contained prompt. Ask for a definitive answer, not a hedged summary. - Cross-check any claim the draft will rely on against at least one primary source. If two sources disagree, note the disagreement in the draft rather than silently picking a 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.
- 2mo ago First seen · 122 lines · 79 tokens per session scan A 9e7d5c9eccbb
draft-issue-to-external-repository is a skill published in the GitHub repository dyoshikawa/rulesync (1,595 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,772 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
draft-issue-to-external-repository compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| draft-issue-to-external-repositorydyoshikawa/rulesync | Skill | 1.6k | today | MIT | A | 79 | Claude Code, Codex |
| opensrcvercel-labs/opensrc | Skill | 3.0k | 1mo ago | Apache-2.0 | A | 103 | Claude Code |
| building-agentsericrisco/rsc-harness | Skill | 555 | 5d ago | MIT | A | 85 | Claude Code, Codex |
| agent-evalericrisco/rsc-harness | Skill | 555 | 5d ago | MIT | A | 79 | Claude Code, Codex |
| prompt-engineeringericrisco/rsc-harness | Skill | 555 | 5d ago | MIT | A | 83 | Claude Code, Codex |
| snipedouard-claude/snip | Skill | 483 | 4d ago | MIT | A | 0 | Claude Code, Codex |
| initPM-Shawn/Abu-Cowork | Skill | 420 | yesterday | Apache-2.0 | A | 21 | Claude Code |