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 2ykwang/agent-skills --skill quick-prgit clone --depth 1 https://github.com/2ykwang/agent-skillsWrote 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/2ykwang/agent-skills/quick-pr)<a href="https://agentmods.dev/skills/2ykwang/agent-skills/quick-pr"><img src="https://agentmods.dev/badge/skills/2ykwang/agent-skills/quick-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.1 | $0.00089 | $0.01302 |
| Opus 5 | $0.00044 | $0.00651 |
| Sonnet 5 | $0.00018 | $0.00260 |
| Haiku 4.5 | $0.00009 | $0.00130 |
Grade A, and why
quick-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick PR
Split an unrelated minor change (convention fix, typo, config tweak) from the current working tree into an independent PR — without leaving the current branch.
This is a Claude Code skill. It requires Claude Code built-in tools: EnterWorktree, ExitWorktree, and AskUserQuestion.
Use this skill when
- A small fix (typo, lint, config) is mixed into a larger feature branch
- The user wants to ship a trivial change immediately without polluting the current PR
- The user says "quick PR", "split this out", or "ship this separately"
Do not use this skill when
- The change is part of the current feature work
- The user only wants a PR description (use
/write-prinstead) - The change requires review or testing beyond a simple visual check
Input
$ARGUMENTS
Argument interpretation:
- File path (e.g.,
src/config.py) — extract the current diff for that file and apply it in the worktree - Description text (e.g.,
"fix typo in README") — make the edit directly in the worktree - Empty — ask the user what to split out
Tools
Fetch these tools via ToolSearch before use:
| Purpose | Tool |
|---|---|
| Enter isolated worktree | EnterWorktree |
| Exit/remove worktree | ExitWorktree |
| Ask the user | AskUserQuestion |
Procedure
Step 1: Determine Change Scope
File path arg: Run git diff HEAD -- <file>, show the diff.
Description arg: Propose which files to modify and how.
Empty arg: Ask what to split out.
→ Use AskUserQuestion to confirm the scope before continuing.
Step 2: Choose Branch Name and Commit Message
Check the project's commit style: git log --oneline -10.
Propose up to 5 candidates for each:
- Branch: kebab-case, prefix
fix/chore/docs/feat/ - Commit: match dominant pattern (Conventional Commits, ticket prefix, etc.); default to Conventional Commits if unclear
→ Use AskUserQuestion with the numbered options. User picks or writes their own.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 152 lines · 89 tokens per session scan A 51d4cd80edf8
quick-pr is a skill published in the GitHub repository 2ykwang/agent-skills (19 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,302 once invoked, about $0.0004 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
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…
plugin-updating
Use this skill when the user asks to bump, update, or release a new version of a plugin in the Shopware AI Coding Tools marketplace — phrases like "bump test-writing to 3.8.0", "release a patch for dev-tooling", "update the plugin version". Handles synchronized version bumps across plugin.json and every SKILL.md…
release-info-writing
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…
openclaw-release-maintainer
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
git-workflow
Git workflow patterns and version control best practices for teams of any size. Use when the user asks to choose a branching strategy (trunk-based, GitHub Flow, Git Flow, GitLab Flow), define commit conventions, set up PR workflows, plan release management, structure a monorepo, or establish team git standards. Covers…