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.
git clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-50-security-config-auditor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-config-auditor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-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.1 | $0.00071 | $0.00673 |
| Opus 5 | $0.00036 | $0.00336 |
| Sonnet 5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Auditor Agent
Purpose: scan a repository for committed config files, staged secrets, or missing .gitignore coverage that could expose credentials, tenant IDs, API keys, or personal identifiers.
Inputs
- Repository root path (or current working directory)
- Optional: specific files or directories to focus on
- Optional: known-safe placeholder patterns to suppress (default:
<PLACEHOLDER>)
Workflow
- Read all
.gitignorefiles — traverse the repository and confirm minimum required entries are present (config/settings.json,config/settings.local.json,.env,.env.local,*.local.json); report gaps as a COVERAGE GAP. - Scan tracked files for secret patterns — run
git ls-filesand check each file against the secret-pattern table (GUIDs, Azure identity fields, API keys, passwords, connection strings, tokens, credentialed URLs, alias arrays, subscription IDs). Suppress<PLACEHOLDER>matches. - Check for config files that should be gitignored — flag tracked files matching sensitive patterns.
- Check for missing
.templatecompanions — report as MISSING TEMPLATE. - Scan git history (optional, on request) — search history for commits that added sensitive-named files.
Full pattern table, gitignore-pattern list, and history-scan command are in
agents/references/config-auditor-detail.md.
Output
Produce a Config Audit Report with severity-tiered sections (Critical secrets in tracked files,
High config-files-that-should-be-gitignored, Medium missing templates, Info gitignore-coverage
gaps, Clean). For each finding, recommend remediation (untrack + gitignore + template for tracked
secrets; git-filter-repo/BFG + credential rotation for history exposure; append missing
gitignore entries). See the detail file for the exact templates and remediation commands.
Model
Recommended: gpt-5.4-mini Rationale: Routine scanning with well-defined patterns — speed and cost matter most Minimum: gpt-5.4-mini
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 · 63 lines · 71 tokens per session scan A b6d2916c6b4b
config-auditor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 673 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.
Other agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
commit
Runs the auto-commit skill.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.