/ Verzeichnis / Playground / Agnix (Agent Config Linter)
● Community avifenesh ⚡ Sofort

Agnix (Agent Config Linter)

von avifenesh · avifenesh/agnix

The missing linter and LSP for AI-coding-assistant configs (CLAUDE.md, SKILL.md, hooks, MCP).

Agnix validates agent configuration files — CLAUDE.md, AGENTS.md, SKILL.md frontmatter, hook scripts, MCP settings — with 156 rules and autofixes. Plugins for VS Code, Zed, Neovim. Treat it like ESLint for your agent setup.

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

agnix-skill.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren 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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "agnix-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/avifenesh/agnix",
        "~/.claude/skills/agnix"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: 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

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

Voraussetzungen
  • Server/skill installed and authenticated — See repo README
Ablauf
  1. Set up CI
    Add agnix check to GitHub Actions on every PR touching .claude/ or skills/.✓ Kopiert
    → Workflow file added
  2. Fix locally
    Run agnix fix on the staged files. Show me the diff before committing.✓ Kopiert
    → Autofix diff

Ergebnis: No more bad-frontmatter incidents in production.

Fallstricke
  • 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.

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
See provider docs for rate limits
Tokens pro Aufruf
Varies by tool
Kosten in €
See repo README for pricing details
Tipp
Cache tool results and avoid repeated identical calls.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Use environment variables; never commit secrets
Datenabfluss: Tool calls go to the provider's API as documented

Fehlerbehebung

Häufige Fehler und Lösungen

rule too strict

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

Prüfen: agnix check --explain <rule-id>
LSP doesn't activate

Make sure the editor extension matches your agnix CLI version.

Prüfen: agnix --version vs extension version

Alternativen

Agnix (Agent Config Linter) vs. andere

AlternativeWann stattdessenKompromiss
Hand-rolled YAML lintersYou only need one formatWon't catch cross-file issues

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen