audit-env-parity

audit-env-parity is a skill for Claude Code, Codex from kensaurus/cursor-kenji. It costs 69 tokens per session (1,310 once invoked), scanned A, original, MIT.

A read-only comparison of configuration names and settings across development, staging, and production environments.

In plain words
What is it for?
Use it to investigate “works locally but not in production” problems and compare which configuration keys exist in each environment.
Why use it?
It finds missing or renamed environment variables, changed feature flags, hardcoded values, and reused secrets that cause local and production behavior to differ.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to investigate “works locally but not in production” problems and compare which configuration keys exist in each environment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kensaurus/cursor-kenji/audit-env-parity
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 kensaurus/cursor-kenji --skill audit-env-parity
Clone the repo
git clone --depth 1 https://github.com/kensaurus/cursor-kenji

Made for: Claude Code, Codex.

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 audit-env-parity

README.md
[![agentmods](https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-env-parity/github.svg)](https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-env-parity)
Your own site
<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-env-parity"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-env-parity/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.

agentmods 80×15 button for audit-env-parity

Your own site · 80×15
<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-env-parity"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-env-parity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,310 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.00069 $0.01310
Opus 5 $0.00034 $0.00655
Sonnet 5 $0.00014 $0.00262
Haiku 4.5 $0.00007 $0.00131

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

Security

Grade A, and why

audit-env-parity 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.

skills/audit-env-parity/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

audit-env-parity — Environments that agree

Degree of freedom: MIXED — Phases 0–1 [HIGH freedom]; Phase 2 three-way name diff [LOW freedom — names only, never values].

Read-only. Find where environments disagree in ways that cause "works on my machine", silent prod misbehavior, or leaked secrets.

The classic outage: a new env var added locally, referenced in code, never set in prod — deploy is green, feature is broken.

Never print secret values. Present the gap matrix; do not change host config until approved.

This skill vs neighbors

Skill Owns
audit-env-parity (this) Same keys exist (and mean the same) in every env
workflow-environment-ready Local machine can build/test/reach services
plan-secrets-audit Credential exposure in git / over-scoped keys
plan-data-integrity Destructive ops; staging pointing at prod is shared
workflow-feature-flag Flag rollout process, not "staging flag ≠ prod flag"

Do not fire for "did I commit a key" → plan-secrets-audit. Do not fire for "prove this laptop can run the suite" → workflow-environment-ready.

How to reason

  1. Observe — quote the process.env / import.meta.env read and whether the name exists in each env
  2. Interpret — which runtime path breaks if that name is missing or public-prefixed?
  3. Classify — referenced-but-unset / naming drift / secret reuse / hardcoded / dead
  4. Severity — prod-missing or public-prefix secret = P0 / Critical

Worked example

Observe: process.env.STRIPE_WEBHOOK_SECRET used in app/api/stripe/route.ts; name absent from Vercel prod; present locally. Interpret: deploy is green; webhook verify fails only in prod. Classify: referenced-but-unset (prod). Severity: P0. Finding: STRIPE_WEBHOOK_SECRET | prod absent | P0 | set the name; never print the value


Phase 0 — Enumerate environments and sources [HIGH freedom]

  • Envs: local, preview/staging, prod
  • Sources: .env*, .env.example, Vercel/Supabase/Fly dashboards, CI secrets, runtime config
  • Demanded set: every process.env.X / import.meta.env / config object read

Read the full file on GitHub · 133 lines

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. 5d ago First seen · 133 lines · 69 tokens per session scan A 008613fafc23

Subscribe to this mod's changes

audit-env-parity is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 11d ago), licensed MIT. It adds 69 tokens to every session and 1,310 once invoked, about $0.0003 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.