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/ersinkoc/security-check/sc-secretsnpx skills add ersinkoc/security-check --skill sc-secretsgit clone --depth 1 https://github.com/ersinkoc/security-checkWrote 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/ersinkoc/security-check/sc-secrets)<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-secrets"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-secrets.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.00022 | $0.01627 |
| Opus 5 | $0.00011 | $0.00813 |
| Sonnet 5 | $0.00004 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
sc-secrets 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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SC: Hardcoded Secrets & Credentials
Purpose
Detects hardcoded secrets, API keys, tokens, passwords, private keys, and credentials embedded in source code, configuration files, and environment files committed to version control. Uses pattern matching for known key formats, entropy analysis for unknown formats, and context analysis to distinguish test keys from production secrets.
Activation
Called by sc-orchestrator during Phase 2. Always runs regardless of detected languages.
Phase 1: Discovery
File Patterns to Search
**/*.ts, **/*.js, **/*.py, **/*.go, **/*.php, **/*.java, **/*.cs,
**/*.rb, **/*.yaml, **/*.yml, **/*.json, **/*.xml, **/*.toml,
**/*.env, **/*.env.*, **/*.cfg, **/*.conf, **/*.ini, **/*.properties,
**/*.config, **/config/*, **/settings/*, **/.env*, **/docker-compose*,
**/*.sh, **/*.bash, **/Dockerfile*, **/.github/workflows/*
Known API Key Patterns
| Service | Pattern | Example Prefix |
|---|---|---|
| AWS Access Key | AKIA[0-9A-Z]{16} |
AKIA... |
| AWS Secret Key | 40-char base64 after aws_secret_access_key |
|
| GitHub Token | ghp_[A-Za-z0-9]{36} |
ghp_... |
| GitHub App Token | ghs_[A-Za-z0-9]{36} |
ghs_... |
| GitLab Token | glpat-[A-Za-z0-9\-]{20} |
glpat-... |
| Stripe Live Key | sk_live_[A-Za-z0-9]{24,} |
sk_live_... |
| Stripe Publishable | pk_live_[A-Za-z0-9]{24,} |
pk_live_... |
| Twilio | SK[0-9a-fA-F]{32} |
SK... |
| SendGrid | SG\.[A-Za-z0-9\-_]{22}\.[A-Za-z0-9\-_]{43} |
SG.... |
| Slack Token | xox[baprs]-[A-Za-z0-9\-]{10,} |
xoxb-... |
| Google API Key | AIza[A-Za-z0-9\-_]{35} |
AIza... |
| Firebase Key | AAAA[A-Za-z0-9_-]{7}:[A-Za-z0-9_-]{140} |
|
| Heroku API Key | [0-9a-fA-F]{8}-[0-9a-fA-F]{4}-...-[0-9a-fA-F]{12} |
UUID format |
| npm Token | npm_[A-Za-z0-9]{36} |
npm_... |
| PyPI Token | pypi-[A-Za-z0-9\-_]{16,} |
pypi-... |
Private Key Detection
"-----BEGIN RSA PRIVATE KEY-----"
"-----BEGIN EC PRIVATE KEY-----"
"-----BEGIN OPENSSH PRIVATE KEY-----"
"-----BEGIN PGP PRIVATE KEY BLOCK-----"
"-----BEGIN DSA PRIVATE KEY-----"
"-----BEGIN PRIVATE KEY-----"
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.
- 5d ago First seen · 137 lines · 22 tokens per session scan A 422b7fd9a4ca
sc-secrets is a skill published in the GitHub repository ersinkoc/security-check (56 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,627 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-30.
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…
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…
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…