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 theashishmaurya/pr-review-agent --skill backendgit clone --depth 1 https://github.com/theashishmaurya/pr-review-agentWrote 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/theashishmaurya/pr-review-agent/backend)<a href="https://agentmods.dev/skills/theashishmaurya/pr-review-agent/backend"><img src="https://agentmods.dev/badge/skills/theashishmaurya/pr-review-agent/backend/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/theashishmaurya/pr-review-agent/backend"><img src="https://agentmods.dev/badge/skills/theashishmaurya/pr-review-agent/backend.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.00013 | $0.00563 |
| Opus 5 | $0.00006 | $0.00282 |
| Sonnet 5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
Backend 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 9d 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
Backend Review Skill
Review backend code for reliability, performance, and API design.
API Design
RESTful Principles
- Correct HTTP methods (GET, POST, PUT, DELETE)
- Proper status codes
- Consistent response format
- Pagination for list endpoints
- Filtering and sorting support
Error Handling
- Meaningful error messages
- Proper HTTP status codes
- Error responses structured
- Stack traces hidden in production
Database
Queries
- N+1 queries identified and fixed
- Indexes used appropriately
- Transactions for related operations
- Pagination for large result sets
- Query timeouts configured
Data Integrity
- Constraints at database level
- Foreign keys properly defined
- Cascade deletes/deletes considered
- Soft deletes vs hard deletes
Performance
- Connection pooling configured
- Caching for frequently accessed data
- Background jobs for slow operations
- Request timeout configured
- Rate limiting implemented
Reliability
- Graceful shutdown implemented
- Health check endpoints
- Logging structured (JSON)
- Metrics exposed
- Error tracking configured
Security
- Input validation on all endpoints
- Authentication middleware
- Authorization checks
- Rate limiting
- CORS configured properly
Code Structure
Layered Architecture
handlers/ -> HTTP handling, validation
services/ -> Business logic
repositories/ -> Data access
- Handlers thin, services contain logic
- Dependency injection
- Interfaces for external dependencies
- Single responsibility
Error Handling
// ❌ Swallowing errors
if err != nil {
log.Println(err)
return nil
}
// ✅ Proper error handling
if err != nil {
return fmt.Errorf("failed to create user: %w", err)
}
Severity Guide
🚨 Error: Data loss, security vulnerability, crash ⚠️ Warning: Performance issue, anti-pattern 💡 Info: Code quality, maintainability
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.
- 9d ago First seen · 106 lines · 13 tokens per session scan A f90bb344f1d8
Backend Review is a skill published in the GitHub repository theashishmaurya/pr-review-agent (2 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 563 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-31.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
api-reviewer
A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.