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/arcblock/agent-skills/pull-requestnpx skills add ArcBlock/agent-skills --skill pull-requestgit clone --depth 1 https://github.com/ArcBlock/agent-skillsWhat 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.00023 | $0.02690 |
| Opus 5 | $0.00012 | $0.01345 |
| Sonnet 5 | $0.00005 | $0.00538 |
| Haiku 4.5 | $0.00002 | $0.00269 |
Grade A, and why
pull-request 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 yesterday.
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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Skill
Generate standardized Pull Requests by analyzing the diff between current branch and main branch.
Step 0: Check for Project PR Template (IMPORTANT)
CRITICAL: Before generating PR content, ALWAYS check if the project has a custom PR template:
# Check for PR template in common locations
ls -la .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || \
ls -la .github/PULL_REQUEST_TEMPLATE/ 2>/dev/null || \
ls -la docs/PULL_REQUEST_TEMPLATE.md 2>/dev/null
If a PR template exists:
- Read the template file using the Read tool
- Use that template's structure for the PR body
- Fill in each section according to the template's format and comments
- Keep any checkboxes or structured lists from the template
If no PR template exists: Use the default template defined below.
PR Template (Default - Use only if no project template exists)
Based on analysis of high-quality PRs, use this template:
Title Format
<type>(<scope>): <description>
Types (same as Conventional Commits):
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Code style changes |
refactor |
Code refactoring |
perf |
Performance improvement |
test |
Add or modify tests |
chore |
Build process or tools |
ci |
CI/CD configuration |
build |
Build system changes |
Scope: Optional, indicates affected module (e.g., agentloop, blocklet, auth)
Description:
- Imperative mood ("add" not "added")
- Lowercase first letter
- No period at end
- Under 72 characters
Body Format
## Summary
<1-5 bullet points describing key changes>
## Motivation / Context
<Why this change is needed - the problem being solved>
## Changes
<Detailed list of what was changed, organized by area>
## Test Plan
<How to verify the changes work correctly>
- [ ] Step 1
- [ ] Step 2
---
Generated with [Claude Code](https://claude.com/claude-code)
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.
- yesterday First seen · 385 lines · 23 tokens per session scan A a188cc706677
pull-request is a skill published in the GitHub repository ArcBlock/agent-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 2,690 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…