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 ruchernchong/claude-kit --skill create-prgit clone --depth 1 https://github.com/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/create-pr)<a href="https://agentmods.dev/skills/ruchernchong/claude-kit/create-pr"><img src="https://agentmods.dev/badge/skills/ruchernchong/claude-kit/create-pr/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/ruchernchong/claude-kit/create-pr"><img src="https://agentmods.dev/badge/skills/ruchernchong/claude-kit/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00016 | $0.00448 |
| Opus 5.5 | $0.00006 | $0.00179 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
create-pr 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 1mo 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
Language Conventions
Infer language style from the project:
- Analyze existing pull requests, commit messages, and documentation to detect the project's language variant (US English, UK English, etc.)
- Match the spelling conventions found in the project (e.g., "optimize" vs "optimise", "favor" vs "favour")
- Maintain consistency with the project's established language style throughout PR titles and descriptions
Create a pull request with the following workflow:
- Check current git status and branch
- Push the current branch to remote (with -u flag if needed)
- Analyse recent commits to generate PR title and description
- Create GitHub PR and auto-assign to current user:
- Use
gh pr create --assignee @meto self-assign the pull request - If assignment fails (user not a collaborator), GitHub CLI will create the PR without assignment
- This provides convenience for repository collaborators while remaining safe for contributors
- Use
- Optional: Additional assignees can be added using
--assigneeflag (comma-separated for multiple)- Note: PR is already auto-assigned to the current user via
--assignee @mein step 4
- Note: PR is already auto-assigned to the current user via
CONCISE PR RULE: Keep everything brief and focused
Generate a title based on the commit history and user's request context.
For the PR title:
- Use natural, descriptive language (NOT conventional commits format like "feat:", "fix:", "chore:")
- Make it clear and specific to the changes
- Keep it concise but informative
For the PR description:
- Maximum 1-2 bullet points summarizing the key changes
- No verbose explanations - be direct and specific
- No test plan, acceptance criteria, or additional sections
- Focus only on what changed and why
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.
- 1mo ago First seen · 44 lines · 16 tokens per session scan A ef29abf489b8
create-pr is a skill published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 448 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
hunk-release
Prepares, publishes, verifies, and curates Hunk releases. Use for release metadata, benchmarks, tags, publishing, release videos, backports, or recovery.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…
uploads-cli
Reference for the uploads CLI and its stdio/hosted MCP tools — exact flags, keys, and contracts for put and attach, screenshot capture, stable PR/issue keys, the managed attachments comment, metadata and search, galleries, change feeds (repo-wide or one PR/issue), config defaults, login/doctor, and output formats. Use…
fix-pr
One-verb pipeline for the operator's highest-frequency manual loop: fetch a PR's unresolved reviewer feedback (inline review comments, review-summary bodies, and issue-level conversation comments) and failing CI checks, triage each issue via parallel read-only probes, fix the validated items in an isolated managed…