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/xxxxxccc/devops-bot/pr-reviewnpx skills add xxxxxccc/devops-bot --skill pr-reviewgit clone --depth 1 https://github.com/xxxxxccc/devops-botWrote 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/xxxxxccc/devops-bot/pr-review)<a href="https://agentmods.dev/skills/xxxxxccc/devops-bot/pr-review"><img src="https://agentmods.dev/badge/skills/xxxxxccc/devops-bot/pr-review.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.00026 | $0.00431 |
| Opus 5 | $0.00013 | $0.00216 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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 5d 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 Guidelines
Review Priority (highest to lowest)
- Security — vulnerabilities, exposed secrets, injection, auth bypass
- Correctness — logic errors, edge cases, data loss, race conditions
- Error Handling — unhandled exceptions, missing null checks, unclear error messages
- Performance — N+1 queries, unbounded loops, memory leaks, blocking I/O
- Maintainability — unclear naming, DRY violations, missing types, excessive complexity
What to Flag
- Breaking API changes without versioning
- Missing input validation on public interfaces
- Hardcoded secrets, credentials, or environment-specific values
- Database queries without indexes (when schema is visible)
- Promises without error handling (
.catchor try/catch) - Resource leaks (unclosed connections, file handles, timers)
What NOT to Flag
- Style/formatting issues (handled by linters/formatters)
- Import ordering
- Trailing whitespace
- Minor naming preferences when existing conventions are followed
- Generated files, lock files, build artifacts
Comment Quality
- Be specific: "Line 42:
users.find()without.lean()returns full Mongoose documents, adding ~30% memory overhead" is better than "Consider performance" - Suggest fixes: Include a code snippet when the fix is non-obvious
- Explain impact: "This could cause a memory leak in long-running processes because..."
- Acknowledge good patterns: "Good use of discriminated unions here for type safety"
Severity Levels
- critical: Must fix before merge. Security issues, data loss risks, correctness bugs.
- warning: Should fix. Performance issues, missing error handling, fragile patterns.
- suggestion: Nice to have. Better approaches, minor improvements.
- nitpick: Purely optional. Naming tweaks, minor style preferences.
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.
- 5d ago First seen · 46 lines · 26 tokens per session scan A 645882b90b21
pr-review is a skill published in the GitHub repository xxxxxccc/devops-bot (47 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 431 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
setup
Add or remove notification channels (telegram, slack, teams, lark, webhook).
add-adapter
Add a vendor-official or community adapter to the Chat SDK catalog and docs — adapters.json registry, chat/adapters catalog entry, the docs MDX page, meta.json, integration-test lists, and a changeset. Use when a developer wants to add, list, register, or submit a third-party (vendor-official or community) adapter to…
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to scaffold a bot with create-chat-sdk, build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files…
update-model-pricing
Verify and refresh AgentConnect's daemon-side public OpenAI fallback pricing, exact model aliases, long-context and cache rules, and regression tests. Use when OpenAI model prices or IDs change, fallback cost becomes missing or stale, codex-acp changes its token mapping, or someone asks to audit or update…
metabase-data-app-semantic-layer
Use when building, creating, or editing data apps that should query Metabase tables and metrics through generated schema files like metabase.data.ts or .metabase.data.ts.
metabase-data-app-setup
Scaffold a new Metabase data-app into the connected remote-sync repository's dataapps/ / directory from the data-app-template. Use when the user asks to start, create, scaffold, or set up a data-app from scratch.