What is config-drift-remediation?

A read-only procedure for finding configuration differences between environments. Configuration files store settings such as endpoints, feature switches, and credentials in formats including .env, YAML, JSON, and Java properties files.

Use it to compare environment configuration, investigate configuration drift, review release changes, and check for plaintext credentials.

It helps identify missing settings, changed data types, renamed keys, and exposed secrets before a release. It also ranks which differences should be addressed first without changing production files.

config-drift-remediation — Skill for Codex by xiaohuxi

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 xiaohuxi/config-drift-guard-mcp --skill config-drift-remediation

Clone the repo

git clone --depth 1 https://github.com/xiaohuxi/config-drift-guard-mcp

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xiaohuxi/config-drift-guard-mcp/config-drift-remediation/github.svg)](https://agentmods.dev/skills/xiaohuxi/config-drift-guard-mcp/config-drift-remediation)

Your own site

<a href="https://agentmods.dev/skills/xiaohuxi/config-drift-guard-mcp/config-drift-remediation"><img src="https://agentmods.dev/badge/skills/xiaohuxi/config-drift-guard-mcp/config-drift-remediation/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/xiaohuxi/config-drift-guard-mcp/config-drift-remediation"><img src="https://agentmods.dev/badge/skills/xiaohuxi/config-drift-guard-mcp/config-drift-remediation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 608 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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.00608
Opus 5.5	$0.00026	$0.00243
Sonnet 5.5	$0.00013	$0.00122
Haiku 4.5	$0.00006	$0.00061

Measured 2mo ago against content hash 810569a5c9ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

config-drift-remediation 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 2mo 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/config-drift-remediation/SKILL.md · 64 lines

How it starts

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

Config Drift Remediation

Use config-drift-guard-mcp as the evidence source. Keep the workflow read-only and never write directly to production configuration.

Workflow

Identify the baseline and target environments.
Confirm the supplied files represent equivalent applications or components.
Call inspect_config for both files.
Stop and report parsing errors, unsupported formats, duplicate keys, or inaccessible paths.
Call compare_configs with the baseline and target files.
Call scan_secrets for both files even when their secret fingerprints are identical; configuration drift and plaintext-secret exposure are separate risks.
Classify every difference:
- Expected environment difference: hostnames, endpoints, replicas, feature switches, or capacities that intentionally vary.
- Missing configuration: required key absent from the target.
- Type drift: equivalent key changes type, such as number to string.
- Structure drift: renamed, moved, or split key paths.
- Sensitive configuration risk: plaintext secret, private key, credential-bearing URL, or unexpected secret fingerprint change.
Rank remediation work:
- Critical: exposed credentials or unexpected secret changes.
- High: missing required keys, type drift, or incompatible structure.
- Medium: non-sensitive value changes needing confirmation.
- Low: documented expected differences.
Produce the report using references/report-template.md.
End with a verification checklist and unresolved decisions.

Guardrails

Never reveal secret plaintext or attempt to recover it; use only MCP-provided masks and fingerprints.
Never copy a secret from one environment into another.
Never assume every difference is an error.
Never modify remote configuration, commit files, or deploy changes without an explicit separate request.
Prefer key-level patch guidance over rewriting whole files.
Preserve target-environment values that are documented as intentional.
Recommend secret rotation when plaintext credentials are detected.

Read the full file on GitHub · 64 lines

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.

2mo ago First seen · 64 lines · 64 tokens per session scan A 810569a5c9ef

Subscribe to this mod's changes

config-drift-remediation is a skill published in the GitHub repository xiaohuxi/config-drift-guard-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 608 once invoked, about $0.0003 per session on Opus 5.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-31.

Debugging DevOps and cloud

config-drift-remediation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
config-drift-remediationxiaohuxi/config-drift-guard-mcp	Skill	0	3mo ago	MIT	A	64	Codex
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	today	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	yesterday	MIT	A	71	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	320	today	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	2.0k	24d ago	MIT	A	36	Claude Code
diagnosing-missing-recordingsPostHog/posthog	Skill	41k	today	none	A	76	Claude Code, Codex