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/stefanthecode/dotnet-ai-toolkit/secrets-config-auditornpx skills add StefanTheCode/dotnet-ai-toolkit --skill secrets-config-auditorgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWrote 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/stefanthecode/dotnet-ai-toolkit/secrets-config-auditor)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/secrets-config-auditor"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/secrets-config-auditor.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.00109 | $0.00664 |
| Opus 5 | $0.00055 | $0.00332 |
| Sonnet 5 | $0.00022 | $0.00133 |
| Haiku 4.5 | $0.00011 | $0.00066 |
Grade A, and why
secrets-config-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets & Config Auditor
Find credentials and secrets that shouldn't be in source or committed config, and move them to a proper secret store.
Input — point it at your project / repo
Works on a target: a project, repo, or GitHub URL. Scan source, config, and (if a repo) committed history hints:
grep -rniE "password\s*=|pwd=|apikey|api_key|secret|connectionstring|bearer |token\s*=|AccessKey|PrivateKey" \
--include=*.cs --include=*.json --include=*.config --include=*.yml <target> | grep -vi "/obj/\|/bin/"
grep -rn "EnableSensitiveDataLogging\|//.*password\|placeholder" <target>
Check appsettings*.json, .env, launchSettings.json, pipeline YAML, and .csproj.
What it flags
- 🔴 Hardcoded secrets in source — keys/passwords/tokens in
.cs. - 🔴 Secrets in committed
appsettings.json— connection strings with passwords, API keys. (Dev secrets belong in user-secrets, prod in a vault.) - 🔴 Secrets in pipeline YAML / Dockerfiles — should be pipeline secret variables.
- 🟡
EnableSensitiveDataLogging()unconditional — leaks parameter values to logs. - 🟡 Weak config hygiene — secrets in
launchSettings.json,.envcommitted, no.gitignorecoverage.
Fix recommendations
- Dev:
dotnet user-secrets(per-project, outside the repo). - Prod: Azure Key Vault / AWS Secrets Manager / HashiCorp Vault, surfaced via configuration providers or env vars.
- CI: pipeline secret variables, never in YAML literals.
- Rotate anything that was committed — it's compromised even after removal (git history).
- Add patterns to
.gitignore; consider a pre-commit secret scanner (gitleaks).
Principles
- A secret in source/committed config is a leaked secret — and history keeps it. Rotate, don't just delete.
- Config should reference secrets, not contain them.
- Different environments, different stores — never one committed file with prod creds.
How to use it & best prompts
"Do I have any hardcoded secrets", "scan my repo for leaked credentials", "is my appsettings safe to commit", "where should these connection strings live". Pairs with the aspnetcore-security-auditor agent.
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 · 42 lines · 109 tokens per session scan A f88859d02429
secrets-config-auditor is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 26d ago), licensed MIT. It adds 109 tokens to every session and 664 once invoked, about $0.0005 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…