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 community-code-reviewergit 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/community-code-reviewer)<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/community-code-reviewer"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/community-code-reviewer/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/community-code-reviewer"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/community-code-reviewer.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.00040 | $0.00379 |
| Opus 5.5 | $0.00016 | $0.00152 |
| Sonnet 5.5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
community-code-reviewer 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.
What it actually says
Code Review Skill
Perform thorough, constructive code reviews on pull requests and code changes.
Instructions
When reviewing code:
1. First Pass - Understanding
- Read the PR description and linked issues
- Understand the intent and context
- Identify the scope of changes
2. Check for Issues
Correctness
- Logic errors or bugs
- Edge cases not handled
- Race conditions or concurrency issues
- Null/undefined handling
Security
- Input validation
- SQL injection, XSS vulnerabilities
- Hardcoded secrets or credentials
- Proper authentication/authorization
Performance
- Unnecessary loops or computations
- N+1 queries
- Memory leaks
- Missing caching opportunities
Maintainability
- Code clarity and readability
- Proper naming conventions
- DRY principle violations
- Missing or unclear comments
Testing
- Test coverage for new code
- Edge cases tested
- Integration tests where needed
3. Provide Feedback
Use this format for each comment:
**[Category]** File:Line
Description of the issue or suggestion.
Suggested fix (if applicable):
\`\`\`
code example
\`\`\`
4. Summary
End with a summary:
- Overall assessment (Approve/Request Changes/Comment)
- Key strengths of the PR
- Critical issues that must be addressed
- Nice-to-have improvements
Tone Guidelines
- Be constructive, not critical
- Explain the "why" behind suggestions
- Acknowledge good practices
- Ask questions rather than make demands
- Offer to help if complex changes needed
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 · 80 lines · 40 tokens per session scan A e3fdda1eece5
community-code-reviewer 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 40 tokens to every session and 379 once invoked, about $0.0002 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…