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 vladkesler/initrunner --skill secret-detectiongit clone --depth 1 https://github.com/vladkesler/initrunnerWrote 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/vladkesler/initrunner/secret-detection)<a href="https://agentmods.dev/skills/vladkesler/initrunner/secret-detection"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/secret-detection.svg" alt="Measured on agentmods" 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.00040 | $0.00649 |
| Opus 5 | $0.00020 | $0.00324 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
secret-detection 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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secret detection skill using ripgrep pattern matching.
When to activate
Always activate this skill regardless of project language. Secrets can appear in any file type.
Scanner commands
Run each pattern separately via shell. Exclude lock files and node_modules from all scans.
AWS credentials
rg -n '(?i)(AKIA[0-9A-Z]{16}|aws.{0,20}secret.{0,20}['\''"][0-9a-zA-Z/+]{40})' --glob '!*.{lock,sum}' --glob '!node_modules/**'
GitHub tokens
rg -n '(ghp_[a-zA-Z0-9]{36}|github_pat_[a-zA-Z0-9]{22}_[a-zA-Z0-9]{59})' --glob '!*.{lock,sum}' --glob '!node_modules/**'
Generic secrets
rg -n '(?i)(password|secret|api_key|apikey|token)\s*[=:]\s*['\''"][^'\''"]{8,}' --glob '*.{py,js,ts,yaml,yml,json,env,toml,cfg,ini,conf}' --glob '!node_modules/**'
Private keys
rg -n 'BEGIN (RSA |EC |OPENSSH )?PRIVATE KEY' --glob '!node_modules/**'
Verification
For each match:
-
Check the file path. Skip these:
.env.examplefiles- Test fixtures and mock data directories
- Documentation and README files
- Lock files (package-lock.json, uv.lock, go.sum)
-
Check the value. Skip if it contains:
- Placeholder strings: "xxx", "changeme", "your-", "example", "TODO", "REPLACE", "insert", "dummy", "fake", "test"
- Empty strings or whitespace-only values
-
Check the context. Skip if:
- The variable is assigned from an environment variable
(
os.environ,process.env) - The value is overridden by runtime config
- The variable is assigned from an environment variable
(
MUST flag
- Real AWS access keys (AKIA prefix + 16 uppercase alphanumeric chars)
- Private key blocks (BEGIN PRIVATE KEY) in source code
- Database connection strings with inline passwords
- Tokens matching known formats (ghp_, sk-live_, xoxb-) that are not placeholders
MUST NOT flag
.env.examplefiles with placeholder values- Test fixtures with fake credentials
- Documentation examples showing credential format
- Lock files (package-lock.json, uv.lock, go.sum, yarn.lock)
- Variables named "secret" or "password" assigned empty strings or placeholder values
- Environment variable references (
${SECRET},os.getenv("SECRET"))
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.
- 8d ago First seen · 82 lines · 40 tokens per session scan A 478dce9e6dfc
secret-detection is a skill published in the GitHub repository vladkesler/initrunner (41 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 649 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-30.
Other skills, from other repositories
Vizra ADK Tool Creation
Build custom tools for Vizra ADK agents - includes patterns for database, API, file, and email tools.
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
Vizra ADK Agent Creation
Create AI agents with Vizra ADK - includes patterns for customer service, data analysis, and content generation agents.
Vizra ADK Workflows
Orchestrate complex multi-agent workflows - sequential, parallel, conditional, and loop patterns.
create-skill
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.