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/jl-cmd/claude-dev-env/pr-name-by-capabilitynpx skills add jl-cmd/claude-dev-env --skill pr-name-by-capabilitygit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWrote 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/jl-cmd/claude-dev-env/pr-name-by-capability)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-name-by-capability"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/pr-name-by-capability.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.00086 | $0.00930 |
| Opus 5 | $0.00043 | $0.00465 |
| Sonnet 5 | $0.00017 | $0.00186 |
| Haiku 4.5 | $0.00009 | $0.00093 |
Grade A, and why
pr-name-by-capability 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 6d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name-by-Capability Audit
Audit a GitHub PR against the name-by-capability rule. Inspect paths and title wording for driver or motive words on reusable capability code, and report violations with capability-oriented rename directions.
Mode routing
First-match routing selects the mode before the audit steps:
preflight-proposalrunspr-name-by-capability preflight-proposal <pr_number> --base-sha <base_sha> --head-sha <head_sha> --worktree <isolated_worktree>under the shared preflight proposal contract. Record each finding with violation or OK-driver classification.audit-onlyis report-only and ends after the findings report.- A user-supplied rename or fix direction follows the existing normal fix workflow.
- Normal mode applies the suggested rename direction by default.
Gotchas
- Name reusable libraries for the action they perform; a first cert caller still leaves the library capability-named. Score reuse potential alongside the PR title.
- Correctly driver-named surfaces (
cert_fix_queue, report routing/locate, unfixable patterns) are OK findings — list them under OK drivers. - Renames and new paths carry the most signal; when a PR expands an already-misnamed package, note the package name too.
When this applies
- User invokes
/pr-name-by-capability <PR>or asks to audit a PR for name-by-capability / capability naming. - PR adds or renames packages/modules, or frames a general shared operation with a driver/motive word (
cert_fix,cert_closeout,portal,export, …).
A missing PR number or URL returns exactly: Give a GitHub PR number or URL to audit for name-by-capability. Resolved targets follow Mode routing.
Constraints
- Report findings plus a suggested rename direction for each violation.
- Suggest renames for paths the PR touched; for an expanded offense, also name the package the PR grew.
- Distinguish violation vs OK driver using
reference/offense-examples.md.
What ships with it
5 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.
- 6d ago First seen · 74 lines · 86 tokens per session scan A 385524784b59
pr-name-by-capability is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 930 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-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.