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/batteryshark/rekit/secrets-scannpx skills add batteryshark/rekit --skill secrets-scangit clone --depth 1 https://github.com/batteryshark/rekitWrote 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/batteryshark/rekit/secrets-scan)<a href="https://agentmods.dev/skills/batteryshark/rekit/secrets-scan"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/secrets-scan.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.00078 | $0.00464 |
| Opus 5 | $0.00039 | $0.00232 |
| Sonnet 5 | $0.00016 | $0.00093 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
secrets-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 4d 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
Secrets Scanner
Find leaked credentials — API keys, tokens, private keys — in a file or a whole tree. Pure-stdlib, read-only, and it redacts every match (never echoes a full secret).
When to use
Checking whether a package, dump, or repo you're analysing carries hard-coded
credentials — either an attacker's exfil target or a victim's leaked keys. Run it on
source, configs, .env, and extracted archives.
What it finds
- Provider patterns (high confidence): AWS access keys, GitHub tokens/PATs, Slack
tokens & webhooks, Google API keys, Stripe keys, OpenAI keys, npm/PyPI tokens,
SendGrid, Twilio, JWTs, and PEM
PRIVATE KEYblocks. - Generic (entropy-gated):
api_key = "…"/password: "…"style assignments whose value is high-entropy and not an obvious placeholder (changeme,${VAR},your_key_here, …) →SECRET.GENERIC_HIGH_ENTROPY.
Every value is redacted to prefix…suffix [N chars]; private keys are reported as
presence only. It never validates a key against a live service — no network, ever.
Usage
rekit run secrets-scan ./package
rekit run secrets-scan ./.env --format json
rekit run secrets-scan ./src --min-entropy 3.5 # stricter generic gate
Prerequisites
- python3 ≥ 3.8 — pure stdlib, nothing to vendor.
Note
Regex/entropy heuristics find candidates, not proof — confirm before acting, and remember a real find means the key should be rotated.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 46 lines · 78 tokens per session scan A c0a00490fe26
secrets-scan is a skill published in the GitHub repository batteryshark/rekit (11 stars, last pushed 26d ago), licensed Apache-2.0. It adds 78 tokens to every session and 464 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…