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 codebygarv/Ai-skills --skill environment-config-auditorgit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/environment-config-auditor)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/environment-config-auditor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/environment-config-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/codebygarv/ai-skills/environment-config-auditor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/environment-config-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00620 |
| Opus 5 | $0.00022 | $0.00310 |
| Sonnet 5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
environment-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 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Review environment/config files (.env, YAML/JSON config, etc.) for consistency across environments — missing variables, inconsistent naming, and unexplained differences that commonly cause "works locally, breaks in prod" bugs.
When to Use
- Comparing config across environments (dev/staging/prod) to spot drift.
- Debugging an issue that only happens in one environment.
- Onboarding a new environment and want to confirm nothing's missing relative to existing ones.
What to Analyze
- Missing variables — a variable present in one environment's config but absent in another, where that's not obviously intentional (e.g. a
DEBUGflag being dev-only is fine; aDATABASE_URLmissing in prod is not). - Naming inconsistency — the same concept named differently across files (
DB_URLin one,DATABASE_URLin another) — a common source of "I set the variable but it's not being picked up" bugs. - Type/format inconsistency — a boolean represented as
"true"in one environment and1in another, where the parsing code might not handle both. - Hardcoded values that should be per-environment — the same value (e.g. an API URL) present identically across all environments, when it plausibly should differ (pointing to a prod API from a dev config).
- Values that look like leftover secrets — flag (don't just silently note) anything that looks like it could be a real credential rather than a placeholder — cross-reference with Secrets Scanner territory if found.
- Unused variables — defined in config but not obviously referenced anywhere the reviewer can see (flag as "worth checking," since absence of visible usage isn't proof of non-use without full codebase access).
Output Format
- Findings grouped by category (Missing Variables, Naming Inconsistency, Type/Format Inconsistency, Suspicious Hardcoded Values, Possible Secrets, Possibly Unused).
- Each finding: the variable(s) involved, which environment(s), and the concrete concern.
- Flag anything that looks like a real secret as top priority, with a pointer to Secrets Scanner for a dedicated deeper pass.
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.
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 · 36 lines · 44 tokens per session scan A a1c52feb966c
environment-config-auditor is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 20d ago), licensed MIT. It adds 44 tokens to every session and 620 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-09-03.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…