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-secret-scangit 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-secret-scan)<a href="https://agentmods.dev/skills/bravew/trove/trove-secret-scan"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-secret-scan/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-secret-scan"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-secret-scan.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.00027 | $0.00419 |
| Opus 5 | $0.00014 | $0.00210 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
trove-secret-scan 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 yesterday.
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
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Secret Scanning
Patterns to Detect
| Pattern | Regex | Severity |
|---|---|---|
| AWS Access Key | AKIA[0-9A-Z]{16} |
Critical |
| AWS Secret Key | [A-Za-z0-9/+=]{40} near "secret" |
Critical |
| GitHub Token | gh[ps]_[A-Za-z0-9_]{36,} |
Critical |
| Slack Token | xox[baprs]-[0-9a-zA-Z-]+ |
Critical |
| Generic API Key | [a-zA-Z0-9]{32,} near "api_key" |
Warning |
| Private Key | -----BEGIN.*PRIVATE KEY----- |
Critical |
| JWT Token | eyJ[A-Za-z0-9_-]+\.eyJ[A-Za-z0-9_-]+ |
Warning |
| Password in URL | ://[^:]+:[^@]+@ |
Critical |
Remediation Steps
- Immediately rotate the exposed credential
- Remove the secret from code
- Add to
.gitignoreif it's a file - Use environment variables or secret manager
- Check git history:
git log --all -p -- <file>for old commits - Consider BFG Repo-Cleaner if secret was ever committed
False Positive Handling
- Test fixtures with dummy keys: annotate with
# noqa: secret - Example/template files: use placeholder format
<YOUR_API_KEY_HERE> - Hash values and UUIDs: not secrets, skip
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.
- yesterday Changed · -2 lines 97c5475b6d7f
- 12d ago First seen · 43 lines · 27 tokens per session scan A ce39d817a55c
trove-secret-scan is a skill published in the GitHub repository bravew/trove (10 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 419 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…