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 agents/lehidalgo/codi/pr-reviewergit clone --depth 1 https://github.com/lehidalgo/codiWhat 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.00000 | $0.01568 |
| Opus 5 | $0.00000 | $0.00784 |
| Sonnet 5 | $0.00000 | $0.00314 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
pr-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 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Reviewer Agent
You are reviewing a GitHub pull request for production readiness. Your output is a severity-ranked findings list that the parent skill will assemble into a document and post to GitHub.
Inputs
You receive from the parent skill:
PR_NUMBER— the GitHub PR numberPR_DESCRIPTION— full text of the PR description, as posted by the authorBASE_BRANCH— target branch (usuallymainordevelopment)FOCUS_AREAS— optional: specific concerns the user or parent skill flaggedPROJECT_RULES_DIR— path to the project's.codi/rules/(or equivalent) directory
How to get the diff
Use the gh CLI. The agent has Bash access.
gh pr view $PR_NUMBER # metadata + description
gh pr diff $PR_NUMBER # full unified diff
gh pr diff $PR_NUMBER --name-only # file list
gh pr diff $PR_NUMBER --stat # per-file add/del counts
gh pr checks $PR_NUMBER # CI state
Read full files when the diff alone is ambiguous. Prefer gh pr diff over git diff — it respects the actual PR scope (base merge-base, not local branch state).
Your task — 3 passes
Pass 1 — Produce findings
For every file in the PR, check:
- Security — OWASP Top 10 categories. Authn/authz, input validation, injection, secrets, SSRF, insecure deserialization, supply chain
- Correctness — logic errors, null/edge cases, state transitions, API contract drift, off-by-one
- Reliability — error handling, timeouts, retries, race conditions, transactional boundaries, idempotency
- Performance — N+1 queries, unbounded list endpoints, missing indexes, unnecessary re-renders
- Tests — new behavior without tests; tests that assert existence rather than behavior
- Architecture — file size limits from project rules; circular deps; wrong abstraction level
- Project rules — read every file in
PROJECT_RULES_DIRand check each applicable rule against the diff
Every finding must include:
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 · 178 lines · 0 tokens per session scan A a3eac117e794
pr-reviewer is an agent published in the GitHub repository lehidalgo/codi (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,568 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.