agentmods.dev

configdrift AGENTS.md

Repository instructions for configdrift, a command-line tool that finds and fixes differences between configuration files in development, staging, and production. It covers YAML, JSON, TOML, and environment files.

In plain words
What is it for?
Use them when changing configdrift, running its Python tests and checks, building the package, or working with its command-line interface.
Why use it?
They give coding agents the project's setup, testing, linting, and packaging rules in one place.

Instructions file for CodexOpenCode

4 6d ago A scan 345 tokens original MIT
View the source file Coding-Dev-Tools/configdrift
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.

agentmods
npx agentmods add instructions/coding-dev-tools/configdrift/agents-md
Clone the repo
git clone --depth 1 https://github.com/Coding-Dev-Tools/configdrift

Made for: Codex, OpenCode.

Per session 345 This file is loaded in full into every session.
When invoked 345 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00345 $0.00345
Opus 5 $0.00172 $0.00172
Sonnet 5 $0.00069 $0.00069
Haiku 4.5 $0.00034 $0.00034

Measured yesterday against content hash 40c483c5ec67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

configdrift AGENTS.md 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 yesterday.

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.

AGENTS.md · 30 lines

What it actually says

configdrift

Purpose

CLI tool that detects and fixes configuration file drift across environments (dev/staging/prod). Supports YAML, JSON, TOML, and .env formats.

Build & Test Commands

  • Install: pip install -e . or pip install git+https://github.com/Coding-Dev-Tools/configdrift.git
  • Test: pytest tests/ (or python -m pytest tests/ -v --tb=short)
  • Lint: ruff check src/ tests/
  • Build: pip install build twine && python -m build && twine check dist/*
  • CLI check: configdrift --help

Architecture

Key directories:

  • src/configdrift/ — Main package (CLI, config parsers, drift detection, compliance)
  • tests/ — Test suite
  • .github/workflows/ — CI/CD (auto-code-review.yml, ci.yml, pages.yml, publish.yml)
  • dist/ — Built distributions

Conventions

  • Language: Python 3.10+
  • Test framework: pytest (with coverage)
  • CI: GitHub Actions (matrix: Python 3.10, 3.11, 3.12, 3.13)
  • Linting: ruff (line-length 120, target py310)
  • Formatting: ruff
  • Package layout: src/ layout with setuptools
  • Type checking: py.typed included
  • Dependencies: typer, rich, pyyaml, tomli, tomli-w
  • CLI entry point: configdrift.cli:app
  • Default branch: main
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. yesterday First seen · 30 lines · 345 tokens per session scan A 40c483c5ec67

Subscribe to this mod's changes

configdrift AGENTS.md is an instructions file published in the GitHub repository Coding-Dev-Tools/configdrift (4 stars, last pushed 6d ago), licensed MIT. It adds 345 tokens to every session, about $0.0017 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-08-31.

LanguagesPlanningTestingcliconfiguration-managementdeveloper-toolsdevops-toolsdrift-detectionenv
Related

Other instructions, from other repositories

zenml CLAUDE.md

Instructions for zenml-io/zenml, covering zenml claude code guidelines, project structure, use zenml docs via mcp, code style & quality standards and commenting policy — explain why, not what.

zenml-io/zenml · 4,696 tokens

zenml AGENTS.md

Instructions for zenml-io/zenml, covering zenml codex agent guidelines, project structure, always-loaded rules, common commands and branches, git, and prs.

zenml-io/zenml · 1,575 tokens

varlock AGENTS.md

Instructions for dmno-dev/varlock, covering project conventions, repo structure, package manager, scripts and binary builds.

dmno-dev/varlock · 1,700 tokens

aghub CLAUDE.md

Instructions for AkaraChen/aghub, covering claude.md, project overview, common commands, build and test.

AkaraChen/aghub · 5,671 tokens

aghub AGENTS.md

Instructions for AkaraChen/aghub, covering aghub knowledge base, structure, where to look, conventions and rust.

AkaraChen/aghub · 1,294 tokens

devopness AGENTS.md

Instructions for devopness/devopness, covering agents, core flow, shared constraints, monorepo structure and git workflow.

devopness/devopness · 570 tokens