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 agentmods add skills/dyoshikawa/rulesync/create-issuenpx skills add dyoshikawa/rulesync --skill create-issuegit clone --depth 1 https://github.com/dyoshikawa/rulesyncWhat 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 | $0.00018 | $0.00462 |
| Opus 5 | $0.00009 | $0.00231 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
create-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 2d 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 GitHub Issue
Step 1: Gather Information
Receive the issue topic from $ARGUMENTS or the user's description.
If the information is insufficient, ask the user to clarify the following:
- What needs to be done (the task or problem)
- Why it needs to be done (the purpose or motivation)
Step 2: Research Context
Before writing the issue, investigate the relevant parts of the codebase to understand:
- Which files and modules are affected
- Existing related code patterns
- Potential impact and scope of the change
Step 3: Draft the Issue
Important: All issue content (title, body, labels) must be written in English, regardless of the language used in the conversation with the user.
Create a well-structured issue with the following sections:
## Summary
A concise one-liner describing what this issue is about.
## Motivation / Purpose
Why this change is needed. Explain the problem, user impact, or improvement opportunity.
## Details
Detailed description of what needs to be done:
- Specific changes required
- Files or modules likely affected
- Acceptance criteria or expected behavior
## Additional Context
Any relevant links, screenshots, or references (if applicable).
Step 4: Assign Labels
First, get the available labels from the repository:
gh label list
Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-defined, minimal domain knowledge required), also assign the good first issue label if it exists in the repository.
Step 5: Create the Issue
gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..."
Step 6: Report Result
Output the created issue URL and a summary of:
- Issue title
- Assigned labels
- Whether
good first issuewas applied and why (or why not)
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.
- 2d ago First seen · 80 lines · 18 tokens per session scan A 9ae739c156db
create-issue is a skill published in the GitHub repository dyoshikawa/rulesync (1,362 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 462 once invoked, about $0.0001 per session on Opus 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
deep-clean
Full-spectrum consolidation of AI agent configuration files. Goes beyond memory-only dream skills: audits and optimizes context files (AGENTS.md/AGENTS.md/GEMINI.md/.cursorrules), rules, skills, and memory. Detects stale references, dead file paths, duplicated rules, stack mismatches, contradictions, vague directives…
turborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines…
skill-creator-openai
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…
skill-creator-anthropic
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…