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/approvenpx skills add dyoshikawa/rulesync --skill approvegit 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.00012 | $0.00440 |
| Opus 5 | $0.00006 | $0.00220 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
approve 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
Approve Pull Request
Approve a pull request using gh pr review --approve.
Input
the user's request
Step 1: Determine the Target PR
Parse the user's request to identify the PR to approve:
Case A: PR number or URL is provided
- Extract the PR number from the argument
- Examples:
123,#123,https://github.com/owner/repo/pull/123
Case B: No argument provided
- Get the PR associated with the current branch:
gh pr view --json number,title,state
Case C: Unable to determine the PR
If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), ask the user to specify which PR to approve.
Step 2: Verify the PR
Before approving, confirm the PR details:
gh pr view <pr_number> --json number,title,state,author,baseRefName,headRefName,isDraft
Check:
- The PR state is
OPEN - The PR is not a draft (
isDraftisfalse) - Display the PR title, number, and author to the user for confirmation
If the PR is not open or is a draft, inform the user and stop.
Step 3: Approve the PR
Execute the approve command:
gh pr review <pr_number> --approve
Important: Only approve ONE PR at a time. If multiple PRs are somehow specified, ask the user which single PR to approve.
If you want to add a comment along with the approval, use the --body option:
gh pr review <pr_number> --approve --body "<approval_comment>"
Step 4: Report Result
After approving:
- Confirm the PR was successfully approved
- Display the approved PR number and title
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 · 76 lines · 12 tokens per session scan A b7e680e5ac19
approve is a skill published in the GitHub repository dyoshikawa/rulesync (1,373 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 440 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.…