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-scrap-issuenpx skills add dyoshikawa/rulesync --skill create-scrap-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.00063 | $0.00420 |
| Opus 5 | $0.00032 | $0.00210 |
| Sonnet 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 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 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.
- 2d 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,373 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 420 once invoked, about $0.0003 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.
memstack-business-scope-of-work
Use this skill when the user says 'scope of work', 'SOW', 'define scope', 'project scope', 'write SOW', 'scope document', or is defining project boundaries, deliverables, and acceptance criteria for a formal engagement. Do NOT use for proposals, contracts, or invoicing.
ap-manager
L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.