agnix

Lint agent configurations across Claude Code, Cursor, Copilot, and Codex CLI.

951|110|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/avifenesh/awesome-slash --skill agnix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agnix
Source: https://github.com/avifenesh/awesome-slash/tree/main/plugins/agnix/skills/agnix
Command: npx skills add https://github.com/avifenesh/awesome-slash --skill agnix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint agent configurations before they disrupt workflows. Validates Skills, Hooks, MCP, Memory, Plugins across Claude Code, Cursor, GitHub Copilot, and Codex CLI.

Core Features & Use Cases

  • Validates agent configuration files against 100 rules to ensure consistency and safety.
  • Checks common configuration issues across CLAUDE.md, SKILL.md, hooks, and MCP definitions.
  • Use Case: When introducing a new skill, run agnix to catch misconfigurations before deployment.

Quick Start

Run agnix . to validate the current project and fix issues with --fix.

Frequently Asked Questions about agnix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate agent configurations in CLAUDE.md to prevent workflow breakages?

You can validate agent configurations by running a linting engine against YAML and JSON rule sets. This checks CLAUDE.md and related files against 100 rules to enforce quality and safety across your agent workflows.

Can I lint hooks and MCP definitions for Claude Code, Cursor, and GitHub Copilot together?

Yes, you can lint hooks and MCP definitions across Claude Code, Cursor, GitHub Copilot, and Codex CLI. The validation engine checks common configuration issues across these varied project workflows simultaneously.

How do I automatically fix invalid agent configuration files?

You can automatically fix invalid agent configurations by running the linter with the --fix mode. This applies automated corrections to your YAML/JSON rule sets and configuration files to resolve detected issues.

What is the best way to enforce strict safety rules when configuring AI agent skills?

The best way to enforce strict safety rules is using the --strict mode during configuration linting. This applies a rules-based validation engine with 100 rules to ensure consistency and safety across skills, hooks, and memory plugins.

Does this agent config linter require any external dependencies to run?

No, this agent config linter does not require any external dependencies to run. It operates independently to validate your configuration files and enforce quality across your AI agent workflows.

Why should I lint agent configs before introducing a new skill?

You should lint agent configs before introducing a new skill to catch misconfigurations before deployment. This prevents workflow disruptions by validating definitions across your entire project structure.