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 Claude-Code-Community-Ireland/claude-code-resources --skill pr-descriptiongit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/pr-description)<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/pr-description"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/pr-description/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/pr-description"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/pr-description.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.03047 |
| Opus 5.5 | $0.00013 | $0.01219 |
| Sonnet 5.5 | $0.00006 | $0.00609 |
| Haiku 4.5 | $0.00003 | $0.00305 |
Grade A, and why
pr-description 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 1mo 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 — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Description Standards
PR Title Conventions
The PR title is the first thing reviewers see. It must communicate the change clearly and concisely.
Format
<type>: <concise description of what changed>
Type Prefixes
| Prefix | Use When |
|---|---|
feat: |
Adding new functionality |
fix: |
Correcting a bug |
refactor: |
Restructuring without behavior change |
docs: |
Documentation only |
test: |
Adding or updating tests |
chore: |
Dependencies, tooling, config |
perf: |
Performance improvement |
style: |
Formatting, whitespace, naming |
ci: |
CI/CD pipeline changes |
revert: |
Reverting a previous change |
Title Rules
- Keep under 72 characters
- Use imperative mood: "Add search endpoint" not "Added search endpoint" or "Adds search endpoint"
- Do not end with a period
- Be specific: "fix: resolve login redirect loop on expired sessions" not "fix: login bug"
- Include ticket number if applicable: "feat: add user search (PROJ-1234)"
Good vs Bad Titles
Bad: "Updates"
Good: "feat: add full-text search to user directory"
Bad: "Fix bug"
Good: "fix: prevent duplicate charge on payment retry"
Bad: "Refactoring the auth module and also fixing some tests and updating docs"
Good: "refactor: extract token validation into dedicated service"
PR Description Template
Every PR should follow a structured description. Use this template as a starting point and adapt to your team's needs.
Standard Template
## Summary
A 1-3 sentence overview of what this PR does and why. This should be understandable
by someone who has not read the code.
## Motivation
Why is this change needed? Link to the issue, bug report, or product requirement
that motivated this work.
Closes #123
## Changes
A bulleted list of the specific changes made:
- Added `SearchService` class with full-text query support
- Created `/api/users/search` endpoint with pagination
- Added search index migration for the users table
- Updated API documentation with new endpoint
## Test Plan
How was this change tested? Be specific.
- [ ] Unit tests for `SearchService` covering empty queries, partial matches, and pagination
- [ ] Integration test for the search endpoint with test database
- [ ] Manual testing: verified search returns expected results in staging
- [ ] Load tested with 10k users in the index
## Screenshots / Recordings
If the change has a visual component, include before/after screenshots or a screen
recording. For API changes, include example request/response pairs.
**Before:**
(screenshot or N/A)
**After:**
(screenshot or N/A)
## Notes for Reviewers
Any additional context that will help reviewers:
- I chose cursor-based pagination over offset because [reason]
- The migration is backward-compatible and can be rolled back
- This depends on PR #456 being merged first
## Checklist
- [ ] Tests pass locally
- [ ] Code follows project style guidelines
- [ ] Documentation updated if needed
- [ ] No secrets or credentials included
- [ ] Migration is reversible (if applicable)
- [ ] Breaking changes documented (if applicable)
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.
- 1mo ago First seen · 446 lines · 32 tokens per session scan A a4344b5cb1bc
pr-description is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 3,047 once invoked, about $0.0001 per session on Opus 5.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-09-03.
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.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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…