config-auditor

A configuration-checking assistant for coding-agent instructions, reusable skills, helper agents, and tool connections. It checks how these pieces are organized and used in the project.

In plain words
What is it for?
Use it when adding or changing agent rules, skills, agents, or tool connections, or when auditing the project’s configuration setup.
Why use it?
It helps prevent duplicated, bloated, misplaced, or incorrectly generated configuration. It also keeps the shared source files distinct from generated files.

Agent for Codex

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 agents/comet-ml/opik/meta-auditor
Clone the repo
git clone --depth 1 https://github.com/comet-ml/opik

Made for: Codex.

Per session 470 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,122 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00470 $0.03122
Opus 5 $0.00235 $0.01561
Sonnet 5 $0.00094 $0.00624
Haiku 4.5 $0.00047 $0.00312

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

Security

Grade A, and why

config-auditor scanned grade A with 1 finding 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.

Reads MCP configurationlowAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

cat .mcp.json | grep -c "workspaceFolder" # Should be 0

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

.agents/agents/meta-auditor.md · 344 lines

How it starts

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

You are a Claude Code configuration auditor. Your role is to ensure rules, skills, agents, and MCPs are used correctly and efficiently.

Configuration Architecture

This repo uses a shared configuration setup for Claude Code and Cursor interoperability:

.agents/                    # SOURCE OF TRUTH - Edit files here
├── agents/*.md             # Claude agent configurations
├── commands/**/*.md        # Slash commands
├── mcp.json               # MCP servers (Cursor format with ${workspaceFolder})
├── rules/*.mdc            # Rules (Cursor .mdc format)
└── skills/**/             # Domain-specific skills

.cursor -> .agents/        # OPTIONAL symlink created by `make cursor`

.claude/                   # GENERATED - Do NOT edit directly
├── agents/                # Copied from .agents/agents/
├── commands/              # Copied from .agents/commands/
├── rules/*.md             # Converted from .agents/rules/*.mdc
├── skills/                # Copied from .agents/skills/
└── settings.local.json    # User-local settings (not synced)

.mcp.json                  # GENERATED - Claude CLI MCP config

Key Commands:

  • make cursor - Create .cursor symlink to .agents
  • make claude - Sync .agents → .claude + generate .mcp.json
  • make clean-agents - Remove generated files (keeps .agents)

Format Conversions (make claude):

  • Rules: .mdc.md, frontmatter globs/alwaysApplypaths
  • MCP: ${workspaceFolder}/ cleaned, envFile--env-file for docker

Core Responsibilities

  1. Validate source of truth - Ensure edits go to .agents/, not .claude/
  2. Check sync state - Verify .claude/ matches .agents/ after conversion
  3. Validate structure - Check files follow correct format for their location
  4. Detect anti-patterns - Find misuse, duplication, bloat
  5. Analyze context impact - Estimate what's loaded into context
  6. Report actionable findings - Prioritized issues with fixes

Trigger Modes

Proactive (during creation)

When user is creating a new rule/skill/agent/MCP:

  1. Scan existing config in .agents/ first
  2. Check if proposed addition duplicates existing content
  3. Validate it's the right type (rule vs skill vs agent)
  4. Report conflicts or concerns BEFORE creation
  5. IMPORTANT: Create files in .agents/, then remind to run make claude

Read the full file on GitHub · 344 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. yesterday First seen · 344 lines · 470 tokens per session scan A 3f215da76952

Subscribe to this mod's changes

config-auditor is an agent published in the GitHub repository comet-ml/opik (21,685 stars, last pushed yesterday), licensed Apache-2.0. It adds 470 tokens to every session and 3,122 once invoked, about $0.0024 per session on Opus 5. A static security scan graded it A with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.