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 research-tool-updatesgit 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/research-tool-updates)<a href="https://agentmods.dev/skills/dyoshikawa/rulesync/research-tool-updates"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/research-tool-updates/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/research-tool-updates"><img src="https://agentmods.dev/badge/skills/dyoshikawa/rulesync/research-tool-updates.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.00050 | $0.03460 |
| Opus 5.5 | $0.00020 | $0.01384 |
| Sonnet 5.5 | $0.00010 | $0.00692 |
| Haiku 4.5 | $0.00005 | $0.00346 |
Grade A, and why
research-tool-updates 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Tool Updates
TARGET = the user's request
Purpose: for every target tool rulesync supports, investigate the tool's recent releases (official release notes / GitHub releases preferred), compare them against rulesync's current implementation, and open a per-tool GitHub issue for any upstream capability rulesync has not yet caught up with. When an issue for that tool already exists, supplement it with a comment instead of filing a duplicate.
The matrix bounds the per-tool research, so a full run also scouts outside it: Step 2.5 looks for coding agents rulesync does not target yet and proposes the strongest ones as new targets, so a tool gaining traction is not missed just because nobody has added it to the matrix by hand.
Step 0: Determine Scope
- If
TARGETis provided, investigate only that tool. Accept either the display name (e.g.,Claude Code) or the--targetsid (e.g.,claudecode). Validate it against the supported tool list from Step 1; if it does not match any known tool, stop and report the valid options. - If
TARGETis empty, investigate all supported target tools.
Step 1: Enumerate Supported Target Tools
Read the Supported Tools and Features matrix in README.md. This matrix
is the authoritative source of what rulesync supports today. Extract, for each
in-scope tool:
- The display name and the
--targetsidentifier. - The currently supported feature columns (
rules,ignore,mcp,commands,subagents,skills,hooks,permissions) and their scope markers, using the legend:- ✅ project mode, 🌏 global mode, 🎮 simulated (project only), 🔧 MCP tool config.
Do not hardcode the tool list from memory — re-read the matrix each run so the skill stays in sync with the README.
Then read references/new-target-watchlist.md in the rulesync-feature-research
skill. It records products that are not targets yet but were worth re-checking,
each with the condition that would change that. Evaluate every entry in the same
run: promote one whose condition is met to a target proposal (a GitHub issue,
after the duplicate check in Step 4-1) and remove it from the file, retire an
entry that can no longer be met, and leave the rest with their rows' current
figures refreshed from this re-check. Report which entries were
promoted, retired or left in the final report.
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 02b869f162b0
- 1mo ago First seen · 333 lines · 50 tokens per session scan A 36eefe8814c3
research-tool-updates is a skill published in the GitHub repository dyoshikawa/rulesync (1,535 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 3,460 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
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
snip
You are an expert at writing declarative YAML filters for snip, a CLI proxy that reduces LLM token consumption by filtering shell output.
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
prompt-engineering
Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…
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.