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/darkcofy/sqlprism/reviewing-prsnpx skills add darkcofy/sqlprism --skill reviewing-prsgit clone --depth 1 https://github.com/darkcofy/sqlprismWrote 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/darkcofy/sqlprism/reviewing-prs)<a href="https://agentmods.dev/skills/darkcofy/sqlprism/reviewing-prs"><img src="https://agentmods.dev/badge/skills/darkcofy/sqlprism/reviewing-prs.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 | $0.00060 | $0.00552 |
| Opus 5 | $0.00030 | $0.00276 |
| Sonnet 5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
reviewing-prs 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 3d 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
PR Review
Workflow
- Fetch PR context using the commands below
- Spawn 3 sub-agents in parallel — one per reviewer persona (see REVIEWERS.md)
- Collect results from all three
- Synthesize into a single review using the format in COMMENT-TEMPLATE.md
- Post the comment to the PR
Step 1: Fetch PR Context
gh pr view <number> --json title,body,baseRefName,headRefName,files,additions,deletions
gh pr diff <number>
gh pr view <number> --json reviews,comments
Pass the PR number, title, diff, and file list to each sub-agent.
Step 2: Spawn Reviewers
Launch all three sub-agents in parallel using the Agent tool. Each agent receives:
- The full PR diff
- The file list with additions/deletions
- The PR description
- Their specific reviewer instructions from REVIEWERS.md
Each sub-agent must return a structured review following the format in their instructions. Do not ask them to post comments — only the main agent posts.
Step 3: Synthesize
Read all three reviews. Deduplicate overlapping findings. Assign a final severity to each issue:
- Critical — must fix before merge (bugs, security, data loss)
- Warning — should fix, but not a blocker
- Suggestion — nice to have, optional
Step 4: Post Comment
gh pr comment <number> --body "$(cat <<'EOF'
<synthesized review — see COMMENT-TEMPLATE.md>
EOF
)"
Boundaries
Always:
- Read the full diff before reviewing
- Run all 3 reviewers in parallel
- Include the issue number from the PR body in the review
- Attribute findings to the reviewer who raised them
Ask first:
- Requesting changes (blocking the PR) vs leaving comments
- If the PR touches more than 500 lines changed
Never:
- Approve or merge the PR automatically
- Edit code or push commits to the PR branch
- Post multiple comments (always one synthesized comment)
What ships with it
2 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.
- 3d ago First seen · 67 lines · 60 tokens per session scan A 24a7558742f0
reviewing-prs is a skill published in the GitHub repository darkcofy/sqlprism (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 552 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…