Agnix (Agent Config Linter) (Claude Skill) — Install & Live Demo

Why use it

Key features

156 lint rules across config formats
Autofix for most rules
LSP for major editors (VS Code, Zed, Neovim)
CI-ready CLI: agnix check
Format-aware: knows the difference between SKILL.md and CLAUDE.md

Live Demo

What it looks like in practice

agnix-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "agnix-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/avifenesh/agnix",
        "~/.claude/skills/agnix"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "agnix-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/avifenesh/agnix",
        "~/.claude/skills/agnix"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "agnix-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/avifenesh/agnix",
        "~/.claude/skills/agnix"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "agnix-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/avifenesh/agnix",
        "~/.claude/skills/agnix"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "agnix-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/avifenesh/agnix",
        "~/.claude/skills/agnix"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "agnix-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/avifenesh/agnix",
          "~/.claude/skills/agnix"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add agnix-skill -- git clone https://github.com/avifenesh/agnix ~/.claude/skills/agnix

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Agnix (Agent Config Linter)

Enforce skill quality in CI before merging to the team's shared skill repo

👤 Teams maintaining a skill library ⏱ ~15 min intermediate

When to use: You don't want a broken SKILL.md frontmatter to ship and break everyone's agent.

Prerequisites

Server/skill installed and authenticated — See repo README

Flow

Set up CI

Add agnix check to GitHub Actions on every PR touching .claude/ or skills/.✓ Copied

→ Workflow file added
Fix locally

Run agnix fix on the staged files. Show me the diff before committing.✓ Copied

→ Autofix diff

Outcome: No more bad-frontmatter incidents in production.

Pitfalls

Some rules are opinion-shaped (e.g., max description length). Tune in .agnix.toml rather than ignoring globally. — Some rules are opinion-shaped (e.g., max description length). Tune in .agnix.toml rather than ignoring globally.

Cost & Limits

What this costs to run

API quota: See provider docs for rate limits
Tokens per call: Varies by tool
Monetary: See repo README for pricing details
Tip: Cache tool results and avoid repeated identical calls.

Security

Permissions, secrets, blast radius

Credential storage: Use environment variables; never commit secrets

Data egress: Tool calls go to the provider's API as documented

Troubleshooting

Common errors and fixes

rule too strict

Tune in .agnix.toml — every rule has severity/disable settings.

Verify: agnix check --explain <rule-id>

LSP doesn't activate

Make sure the editor extension matches your agnix CLI version.

Verify: agnix --version vs extension version

Alternatives

Agnix (Agent Config Linter) vs others

Alternative	When to use it instead	Tradeoff
Hand-rolled YAML linters	You only need one format	Won't catch cross-file issues

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills