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/clean-branchesnpx skills add dyoshikawa/rulesync --skill clean-branchesgit 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.00016 | $0.00433 |
| Opus 5 | $0.00008 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
clean-branches 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 3d 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
Clean Branches
Clean up unnecessary local branches and prune stale remote-tracking branches.
Step 1: Inspect Current State
Run the following:
git branch --show-currentgit branch --format='%(refname:short)'git remote show origingit branch -vv
Identify:
- The current branch
- The default branch (for example
mainormaster) - Branches whose upstream has been deleted
After identifying the default branch, list branches already merged into it:
git branch --merged <default-branch>
If you want to use the remote-tracking branch as the source of truth, use:
git branch --merged origin/<default-branch>
Step 2: Refresh Remote State
Update remote refs and prune deleted remote branches:
git fetch --prune
If needed, also run:
git remote prune origin
Step 3: Select Branches to Delete
Delete only branches that are clearly unnecessary.
Safe candidates include:
- Local branches already merged into the default branch you identified above
- Local branches whose upstream branch is gone and are no longer needed
Never delete:
- The current branch
- The default branch
- Branches that are not fully merged unless the user explicitly asks for force deletion
If there is any ambiguity, show the candidate branches to the user and ask for confirmation.
Step 4: Delete Branches
For merged branches, delete them safely:
git branch -d <branch-name>
Only if the user explicitly approves force deletion for unmerged branches, use:
git branch -D <branch-name>
Delete branches one by one, not with a broad wildcard command.
Step 5: Report Result
Summarize:
- Which branches were deleted
- Which branches were skipped and why
- Whether stale remote-tracking branches were pruned
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.
- 3d ago First seen · 89 lines · 16 tokens per session scan A a7c398597275
clean-branches is a skill published in the GitHub repository dyoshikawa/rulesync (1,373 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 433 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…
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.
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.
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.…