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 allsmog/vuln-scout --skill secret-scanninggit clone --depth 1 https://github.com/allsmog/vuln-scoutWrote 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/allsmog/vuln-scout/secret-scanning)<a href="https://agentmods.dev/skills/allsmog/vuln-scout/secret-scanning"><img src="https://agentmods.dev/badge/skills/allsmog/vuln-scout/secret-scanning/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/allsmog/vuln-scout/secret-scanning"><img src="https://agentmods.dev/badge/skills/allsmog/vuln-scout/secret-scanning.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.00067 | $0.02109 |
| Opus 5 | $0.00034 | $0.01055 |
| Sonnet 5 | $0.00013 | $0.00422 |
| Haiku 4.5 | $0.00007 | $0.00211 |
Grade A, and why
Secret Scanning 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 11d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secret Scanning Reference
Purpose
Detect hardcoded secrets, API keys, credentials, and sensitive tokens in source code and git history. Secrets in code are among the most common and highest-impact findings in real-world penetration tests.
When to Use
Activate this skill during:
- Initial code review phase to find low-hanging fruit
- Git history analysis for rotated but exposed credentials
.envand configuration file review- CI/CD pipeline security assessment
High-Value Secret Patterns
API Keys & Tokens
| Pattern | Regex | Severity |
|---|---|---|
| AWS Access Key | AKIA[0-9A-Z]{16} |
CRITICAL |
| AWS Secret Key | [0-9a-zA-Z/+]{40} (near AWS context) |
CRITICAL |
| GitHub Token | ghp_[0-9a-zA-Z]{36} |
HIGH |
| GitHub OAuth | gho_[0-9a-zA-Z]{36} |
HIGH |
| GitLab Token | glpat-[0-9a-zA-Z\-]{20} |
HIGH |
| Slack Bot Token | xoxb-[0-9]{10,13}-[0-9]{10,13}-[a-zA-Z0-9]{24} |
HIGH |
| Slack Webhook | https://hooks\.slack\.com/services/T[A-Z0-9]+/B[A-Z0-9]+/[a-zA-Z0-9]+ |
MEDIUM |
| Stripe Secret Key | sk_live_[0-9a-zA-Z]{24,} |
CRITICAL |
| Stripe Publishable | pk_live_[0-9a-zA-Z]{24,} |
LOW |
| Google API Key | AIza[0-9A-Za-z\-_]{35} |
HIGH |
| Twilio API Key | SK[0-9a-fA-F]{32} |
HIGH |
| SendGrid API Key | SG\.[0-9A-Za-z\-_]{22}\.[0-9A-Za-z\-_]{43} |
HIGH |
Private Keys & Certificates
| Pattern | Indicator | Severity |
|---|---|---|
| RSA Private Key | -----BEGIN RSA PRIVATE KEY----- |
CRITICAL |
| EC Private Key | -----BEGIN EC PRIVATE KEY----- |
CRITICAL |
| PGP Private Key | -----BEGIN PGP PRIVATE KEY BLOCK----- |
CRITICAL |
| SSH Private Key | -----BEGIN OPENSSH PRIVATE KEY----- |
CRITICAL |
| PKCS8 Key | -----BEGIN PRIVATE KEY----- |
CRITICAL |
| Certificate | -----BEGIN CERTIFICATE----- |
LOW |
Database Credentials
| Pattern | Regex | Severity |
|---|---|---|
| Connection String | `(postgres | mysql |
| Redis URL | redis://:[^@]+@ |
HIGH |
| JDBC URL | `jdbc:(mysql | postgresql |
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.
- 11d ago First seen · 194 lines · 67 tokens per session scan A 0e1d644e2bde
Secret Scanning is a skill published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 2,109 once invoked, about $0.0003 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
sast-config
Reviews and tunes SAST tool configurations against OWASP ASVS 4.0.3 and CWE Top 25. Auto-invoked when reviewing Semgrep rules, CodeQL queries, SAST CI integration, or false positive triage workflows. Produces a SAST maturity assessment covering rule authoring, severity tuning, custom rule development, and CI…
sast-semgrep
Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping. Use when: (1) Scanning code for security vulnerabilities across multiple languages, (2) Performing security code reviews with pattern-based…
sast-semgrep
Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping. Use when: (1) Scanning code for security vulnerabilities across multiple languages, (2) Performing security code reviews with pattern-based…
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.