agentmods.dev

config-secrets-audit

config-secrets-audit is a skill for Claude Code from ivegamsft/basecoat. It costs 80 tokens per session (566 once invoked), scanned A, original, MIT.

A repository scan for likely secrets in configuration and infrastructure files. It checks places such as environment files, YAML, GitHub Actions, Bicep, Terraform, and Azure Key Vault references.

In plain words
What is it for?
Use it to detect hardcoded secrets and risky configuration patterns, review findings by severity, add exclusions or custom patterns, and generate SARIF reports.
Why use it?
It helps find credentials, connection strings, and other sensitive values that may have been exposed in source-controlled configuration. Findings can be classified by severity and exported for code-scanning systems.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 4repo today A scan 80 tokens original MIT

Good fit Use it to detect hardcoded secrets and risky configuration patterns, review findings by severity, add exclusions or custom patterns, and generate SARIF reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ivegamsft/basecoat/config-secrets-audit
View source ↗ ivegamsft/basecoat ivegamsft.github.io
Install

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.

Any agent
npx skills add ivegamsft/basecoat --skill config-secrets-audit
Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat

Made for: Claude Code.

Wrote 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.

agentmods badge for config-secrets-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivegamsft/basecoat/config-secrets-audit.svg)](https://agentmods.dev/skills/ivegamsft/basecoat/config-secrets-audit)
Your own site
<a href="https://agentmods.dev/skills/ivegamsft/basecoat/config-secrets-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/config-secrets-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 566 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.00566
Opus 5 $0.00040 $0.00283
Sonnet 5 $0.00016 $0.00113
Haiku 4.5 $0.00008 $0.00057

Measured 4d ago against content hash b15d38588c77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

config-secrets-audit 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/audit-config-secrets.ps1), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/config-secrets-audit/SKILL.md · 59 lines

What it actually says

Config Secrets Audit Skill

Use this skill to identify likely secrets exposure in configuration surfaces and produce CI-ingestable findings.

Core Coverage

  1. Azure Key Vault reference usage checks
  2. Hardcoded connection string detection
  3. GitHub Actions workflow env: secret exposure checks
  4. Base64-like secret token detection
  5. YAML and .env configuration scanning
  6. Bicep/Terraform parameter secret checks
  7. Severity classification (critical, high, medium, low)
  8. SARIF output for code-scanning ingestion
  9. Exclusion and custom-regex extensibility
  10. Summary report grouped by category and severity

Scripts

Script Purpose
scripts/audit-config-secrets.ps1 Runs pattern-based config secret scanning and optionally emits SARIF
  1. Run scanner in repo root and review summary findings.
  2. Triage by severity:
    • critical: direct credential material or production secret literals
    • high: probable secret exposure in workflows or config
    • medium: risky patterns needing review
    • low: informational or potentially safe references
  3. Re-run with exclusions for known-safe patterns.
  4. Export SARIF and upload to code scanning in CI.

Example Commands

pwsh skills/config-secrets-audit/scripts/audit-config-secrets.ps1 -RootPath . -SarifPath .\artifacts\config-secrets.sarif
pwsh skills/config-secrets-audit/scripts/audit-config-secrets.ps1 -RootPath . -ExclusionFile .\config\secret-audit-exclusions.txt
pwsh skills/config-secrets-audit/scripts/audit-config-secrets.ps1 -RootPath . -CustomPatternFile .\config\secret-patterns.json

Integration Notes

  • For Azure policy and compliance rollups, forward SARIF + summary output into your policy reporting pipeline.
  • Use with github-security-posture, security-analyst, or devops-audit for remediation planning.
Files

What ships with it

2 files 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.

Changes

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.

  1. 4d ago First seen · 59 lines · 80 tokens per session scan A b15d38588c77

Subscribe to this mod's changes

config-secrets-audit is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 566 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-09-03.

Security
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens