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 bostonaholic/rpikit --skill security-reviewgit clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/security-review)<a href="https://agentmods.dev/skills/bostonaholic/rpikit/security-review"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/security-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/bostonaholic/rpikit/security-review"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.01376 |
| Opus 5 | $0.00020 | $0.00688 |
| Sonnet 5 | $0.00008 | $0.00275 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
security-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 12d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review Methodology
Review implementation changes for security vulnerabilities and risks.
Purpose
This skill provides methodology for reviewing code changes introduced during implementation. Unlike full codebase audits, this focuses on the delta - what was added or modified - to catch security issues before they're committed.
Review Scope
Determine Changed Files
Identify what was modified during implementation:
- Files created or modified in the current session
- Changes visible in git diff (staged and unstaged)
- New dependencies added
Categorize by Risk Level
High-Risk Changes (require thorough review):
- Authentication/authorization logic
- Input handling and validation
- Database queries and data access
- API endpoints and route handlers
- Cryptographic operations
- File system operations
- External service integrations
- Configuration changes
Medium-Risk Changes:
- Business logic with data transformations
- Error handling and logging
- Session management
- Form processing
Low-Risk Changes:
- UI/styling changes
- Documentation
- Test files (unless testing security features)
Security Checklist
Input Validation
- All user inputs validated before use
- Validation happens server-side (not just client)
- Input length limits enforced
- Type checking performed
- Allowlists preferred over denylists
Injection Prevention
- SQL queries use parameterized statements
- No string concatenation in queries
- Shell commands avoid user input (or properly escaped)
- No eval() or dynamic code execution with user data
- Template rendering escapes output by default
Authentication & Authorization
- Authentication required for protected routes
- Authorization checks at each access point
- No hardcoded credentials
- Secrets loaded from environment/config (not code)
- Session tokens properly validated
Data Protection
- Sensitive data not logged
- PII handled according to requirements
- Passwords hashed with strong algorithms (bcrypt, argon2)
- Encryption used for sensitive data at rest
- HTTPS enforced for data in transit
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.
- 12d ago First seen · 255 lines · 41 tokens per session scan A 6edf6735432f
security-review is a skill published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 1,376 once invoked, about $0.0002 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
cross-review
Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean.
cocoreview
CocoReview — structured code review with six-severity findings vocabulary, progressive disclosure architecture, and universal anti-pattern baseline. Invoked via $review [file] [--complexity] [--security] [--architecture] [--language ].
sentinel
CocoSentinel — eight-dimension artifact quality gate. Dimension G evidence pre-gate runs first (deterministic, .
review
Enter the Review phase of CocoBrew. Aggregates findings from Code Quality Advisor, CocoCupper intelligence, spec compliance check, and decision coverage gate. Produces review.md with decision points. Requires developer approval before $ship can proceed.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
sentinel-approve
CocoSentinel approval — records SHA-bound approval for a previously evaluated artifact. Invoked via $sentinel --approve [file]. Voids automatically if the artifact is modified after approval.