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 bravew/trove --skill trove-security-reviewgit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-security-review)<a href="https://agentmods.dev/skills/bravew/trove/trove-security-review"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-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/bravew/trove/trove-security-review"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-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.00030 | $0.00506 |
| Opus 5 | $0.00015 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
trove-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 10d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Security Review Guidelines
OWASP Top 10 Checklist
1. Injection (SQL, NoSQL, Command)
- All queries use parameterized statements
- User input is never concatenated into queries/commands
- ORM methods are preferred over raw queries
2. Broken Authentication
- Passwords hashed with bcrypt/argon2 (not MD5/SHA1)
- Session tokens are cryptographically random
- Failed login attempts are rate-limited
3. Sensitive Data Exposure
- Secrets stored in env vars / secret managers (never in code)
- PII is encrypted at rest
- HTTPS enforced for all endpoints
4. Broken Access Control
- Authorization checked on every endpoint
- Users can only access their own resources
- Admin endpoints have explicit role checks
5. Security Misconfiguration
- CORS origins are explicitly listed (not
*) - Debug mode is disabled in production
- Default credentials are changed
Secret Detection Patterns
Flag any occurrences of:
- API keys, tokens, passwords in source code
.envfiles committed to git- Hardcoded connection strings with credentials
- Private keys or certificates in repos
For systematic secret detection across the whole tree, hand off to
trove-secret-scan — it's this skill's benefits-from for that
specific reason. Use it as a delegated, bounded sub-agent (input:
"scan everything under src/ for secret patterns"; expected output:
file:line + pattern type or "clean"). See
docs/orchestration.md for delegation
phrasing.
Output Format
## Security Review
### 🔴 Critical Vulnerabilities
- [file:line] [CWE-XXX] Description and fix
### 🟡 Security Warnings
- [file:line] Description and recommendation
### ✅ Security Positives
- Good practices observed
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.
- 10d ago First seen · 73 lines · 30 tokens per session scan A 04a085eb7ece
trove-security-review is a skill published in the GitHub repository bravew/trove (10 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 506 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-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…