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 create-scrap-issuegit 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/create-scrap-issue)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/create-scrap-issue"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/create-scrap-issue/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/create-scrap-issue"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/create-scrap-issue.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.00063 | $0.00420 |
| Opus 5.5 | $0.00025 | $0.00168 |
| Sonnet 5.5 | $0.00013 | $0.00084 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
create-scrap-issue 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
Create a single GitHub issue that consolidates all the content provided by the user.
Requirements
- Write the issue entirely in English.
- Always attach the
maintainer-scraplabel to the issue. - Additionally, judge whether other labels are appropriate based on the content and attach them as needed. For example:
bug— if the content describes a defect or unexpected behaviorenhancement— if the content proposes a new feature or improvementdocumentation— if the content relates to docs updatesrefactor— if the content discusses code restructuring- Use
gh label listto check available labels in the repository before attaching.
- Structure the issue so it is easy to understand even when revisited later:
- Background: Describe the context, motivation, and why this matters.
- Details: Include the specific content, observations, or problems passed by the user.
- Solution / Next Steps: Propose a solution or outline actionable next steps.
- Use a clear, descriptive title that summarizes the scrap topic.
- Use
gh issue createto create the issue.
Workflow
- Review the content provided by the user.
- Organize and enrich it with background information and proposed solutions.
- Check available labels with
gh label listand determine which labels to attach in addition tomaintainer-scrap. - Draft the issue body in the structure above.
- Create the issue with the appropriate labels using
gh issue create --label maintainer-scrap --label <other-labels>.
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 · 38 lines · 63 tokens per session scan A 579f860121a9
create-scrap-issue is a skill published in the GitHub repository dyoshikawa/rulesync (1,530 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 420 once invoked, about $0.0003 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
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
requirement-delivery
A workflow for turning a new software request into a small, working deliverable. It clarifies acceptance criteria, identifies boundaries, breaks work into demonstrable parts, and looks for existing code or tools to reuse.
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…