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/leekjay/claude-skills-plugin/pull-request-guidelinesnpx skills add LeekJay/claude-skills-plugin --skill pull-request-guidelinesgit clone --depth 1 https://github.com/LeekJay/claude-skills-pluginWrote 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/leekjay/claude-skills-plugin/pull-request-guidelines)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/pull-request-guidelines"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/pull-request-guidelines.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.00048 | $0.00717 |
| Opus 5 | $0.00024 | $0.00358 |
| Sonnet 5 | $0.00010 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
pull-request-guidelines 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Guidelines
Standardize Pull Request workflow to ensure code quality, traceability, and efficient code review.
PR Title
Follow Conventional Commits format:
<type>(<scope>): <Chinese subject>
Examples:
- ✅
feat(auth): 添加 OAuth 2.0 登录支持 - ✅
fix(api): 修复用户列表分页问题
PR Description Must Include
1. Chinese Summary
Clearly describe in Chinese:
- What does this PR do?
- Why is this change needed?
- What problem does it solve?
2. Related Issue Links
Closes #123
Related to #456
3. Verification Steps
Automated Checks
-
pnpm lintpasses -
pnpm formatpasses -
pnpm typecheckpasses -
pnpm testpasses
Manual Testing
- Specific test steps
- Expected results
- Test environment info
4. Impact Assessment
Include:
- Database migration requirements
- Configuration changes
- API changes
- Backward compatibility
Pre-Review Checklist
- Local lint passes
- Code formatting complete
- Type checking passes
- Tests pass
- No type assertions (unless justified and documented)
- Commit messages follow conventions
- No AI identifiers
- Manual testing complete
- Documentation updated (if necessary)
PR Template Example
## Summary
[Chinese description of main changes and purpose]
## Related Issues
Closes #[issue number]
## Main Changes
- [Change 1]
- [Change 2]
## Verification Steps
### Automated Checks
- [ ] `pnpm lint` passes
- [ ] `pnpm format` passes
- [ ] `pnpm typecheck` passes
- [ ] `pnpm test` passes
### Manual Testing
1. [Test step 1]
2. [Test step 2]
## Impact Assessment
### Database Migration
- [ ] Migration needed / [x] No migration
### Configuration Changes
- [ ] New env variables / [x] No config changes
### API Changes
- [ ] Breaking changes / [x] Backward compatible
Code Review Guidelines
Reviewer focus areas:
- Functional correctness: Does the code implement expected functionality?
- Code quality: Does it follow project standards and best practices?
- Test coverage: Are there adequate tests?
- Performance: Are there performance issues?
- Security: Are there security vulnerabilities?
- Maintainability: Is the code easy to understand and maintain?
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 · 136 lines · 48 tokens per session scan A c93c9e3b092d
pull-request-guidelines is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 48 tokens to every session and 717 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…