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/dryvist/claude-code-plugins/pr-standardsnpx skills add dryvist/claude-code-plugins --skill pr-standardsgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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.02154 |
| Opus 5 | $0.00012 | $0.01077 |
| Sonnet 5 | $0.00005 | $0.00431 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
pr-standards 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 2d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR & Issue Standards
PR Creation Guards
Run these checks in order before gh pr create. Replace <default> with the
repo's actual default branch — main on a trunk repo, develop on a git-flow
repo (see gh-cli-patterns, github-workflows, for detection).
[!IMPORTANT] For Git Flow repositories, feature and bugfix PRs must always target
develop. You must also add a checklist item to the session plan to mergedevelopintomain(using/promote-release) before wrapping up the session.
Guard 1 — Check for merged twin (prevents zombie PRs):
gh pr list --repo JacobPEvans/<repo> --state merged --head <branch>
If merged PR exists AND git log origin/<default>..HEAD --oneline is empty:
STOP. Remove stale worktree.
Guard 2 — Check for existing open PR (prevents duplicates):
gh pr list --repo JacobPEvans/<repo> --state open --head <branch>
If open PR exists: git push origin <branch> instead of creating new PR.
Guard 3 — Find related issues (enforces linking):
gh issue list --repo JacobPEvans/<repo> --state open --search "<keywords>"
Include Closes #X or Related to #X in PR body. After creation:
gh issue comment <num> --body "Implementation: #<pr>".
This guard only searches GitHub issues — code/repo defects. If the PR resolves
an operational incident, reference the Zammad ticket in prose instead (see
Issue-PR Bidirectional Linking below).
Guard 4 — Validate branch has commits:
git log origin/<default>..HEAD --oneline
If empty: no new work. Clean up instead.
Human-Review Gate (human:review label)
human:review (org label, neon lime, synced to every repo from dryvist/.github
labels.yml) is how an AI flow asks for a human before a PR merges. It is the
human counterpart to the ai:* review-state labels.
Scope — requesting is main-only; the prohibition is unconditional. Only a PR
targeting main can have review requested: merges into develop on a git-flow
repo are always AI-initiated, so never apply the label to a develop-targeted PR.
That scope governs where you may apply the label — not whether to honor one
already present. If any PR carries human:review, whatever its base, a human put
it there deliberately: the merge prohibition below applies and the gate fails
closed.
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.
- 2d ago First seen · 238 lines · 23 tokens per session scan A 88d0ddbe6cd2
pr-standards is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,154 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
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…