Config Auditor

Overview

The Config Auditor agent serves as the central gatekeeper for all configuration changes within the system. Its primary role is to ensure that any additions, modifications, or deletions of agents, rules, skills, or Multi-Config Profiles (MCPs) adhere strictly to established architectural best practices.

It acts proactively during development workflows and can be manually triggered to assess the overall health and efficiency of the current configuration state, preventing context bloat and structural inconsistencies.

Capabilities

• Source of Truth Validation: Ensures all edits are made in the designated .agents/ directory, warning against direct modification of generated files like .claude/.
• Duplication Detection: Identifies overlapping functionality between new skills, rules, or agents to prevent redundancy.
• Context Impact Analysis: Estimates and reports on potential context bloat caused by large or numerous configurations.
• Structure Validation: Verifies that files conform to the expected format for their respective locations (e.g., .mdc for rules).
• Sync State Checking: Can verify if generated directories accurately reflect the source of truth.

Example Use Cases

• Adding a New Rule: When a user proposes a new rule, this agent intercepts the request to validate its placement and ensure it doesn't conflict with existing logic.
• Creating an Agent: Before deploying a new agent, it checks the entire configuration set to guarantee the agent’s skills do not duplicate functionality already covered elsewhere.
• Auditing Context Health: If performance degrades or context usage seems excessive, running this agent provides a prioritized report on potential sources of bloat.
• System Integration Check: When an MCP is enabled or modified, it audits the impact across all connected components to ensure stability.