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 mizukaizen/hive-doctrine-mcp --skill pr-reviewgit clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcpWrote 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/mizukaizen/hive-doctrine-mcp/pr-review)<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/pr-review"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/pr-review/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/mizukaizen/hive-doctrine-mcp/pr-review"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/pr-review.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.00000 | $0.00521 |
| Opus 5.5 | $0.00000 | $0.00208 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
pr-review 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 2mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Pull Request Review
Use when reviewing a pull request. Provides a structured review process that checks code quality, test coverage, breaking changes, and documentation completeness.
Trigger
Invoke this skill when the user asks to review a PR, when a new PR is opened, or when using the reviewer agent.
Process
1. Understand the PR
- Read the PR description and linked issue
- Understand the intent: What problem does this solve?
- Check the size: If over 500 changed lines, recommend splitting
2. Review the Diff
Go through every changed file. For each file, check:
Correctness:
- Does the logic correctly solve the stated problem?
- Are edge cases handled (null, empty, boundary values)?
- Are concurrent access patterns safe?
Breaking Changes:
- Any public API signature changes?
- Any removed or renamed exports?
- Any changed default values or behaviour?
- Any modified configuration format?
If breaking changes are found, verify:
- The PR title or description acknowledges the breaking change
- A migration path is documented
- The version will be bumped appropriately (major)
Test Coverage:
- New features have corresponding tests
- Bug fixes include a regression test
- Tests actually assert meaningful behaviour (not just "does not throw")
Documentation:
- Public API changes reflected in docs
- README updated if user-facing behaviour changed
- Inline comments for non-obvious logic
3. Write the Review
## Review Summary
**PR:** #[number] — [title]
**Verdict:** Approve / Request Changes / Comment
### Breaking Changes
[List or "None detected"]
### Must Fix
- [ ] [File:line] — [Issue description and suggestion]
### Should Fix
- [ ] [File:line] — [Issue description and suggestion]
### Nits
- [File:line] — [Optional improvement]
### Positives
- [What the contributor did well]
4. Apply the Review
If using GitHub CLI:
gh pr review [number] --approve
# or
gh pr review [number] --request-changes --body "Review comments..."
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.
- 2mo ago First seen · 84 lines · 0 tokens per session scan A a624595f5e84
pr-review is a skill published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 521 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.
pr-review compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pr-reviewmizukaizen/hive-doctrine-mcp | Skill | 0 | 4mo ago | MIT | A | 0 | Claude Code, Codex |
| java-best-practicesTaoidle/plan-cascade | Skill | 133 | 7mo ago | MIT | A | 32 | Claude Code |
| release-pr-reviewcyanheads/shift-mcp-server | Skill | 1 | 21d ago | Apache-2.0 | A | 136 | Claude Code |
| code-simplifiercyanheads/shift-mcp-server | Skill | 1 | 21d ago | Apache-2.0 | A | 160 | Claude Code |
| issuejeremylongshore/tons-of-skills-marketplace | Skill | 2.9k | today | MIT | A | 115 | Claude Code |
| link-checkjmagly/aiwg | Skill | 229 | yesterday | MIT | A | 29 | Claude Code, Codex |
| great_ctoavelikiy/great_cto | Skill | 112 | 2d ago | MIT | A | 32 | Claude Code |