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/ruchernchong/claude-kit/create-prnpx 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.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00448 |
| Opus 5 | $0.00008 | $0.00224 |
| Sonnet 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 4d 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.
- 4d 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 3mo ago), licensed MIT. It adds 16 tokens to every session and 448 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-09-01.
Other skills, from other repositories
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.