Agnix (Agent Config Linter) (Claude Skill) — 安裝 & 即時演示

為什麼要用

核心特性

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

即時演示

實際使用效果

agnix-skill.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

~/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
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

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

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

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit

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

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

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

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

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

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

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

加入 context_servers。Zed 儲存後熱重載。

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

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： 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

何時使用： You don't want a broken SKILL.md frontmatter to ship and break everyone's agent.

前置條件

Server/skill installed and authenticated — See repo README

步驟

Set up CI

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

→ Workflow file added
Fix locally

Run agnix fix on the staged files. Show me the diff before committing.✓ 已複製

→ Autofix diff

結果： No more bad-frontmatter incidents in production.

注意事項

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.

成本與限制

運行它的成本

API 配額: See provider docs for rate limits
每次呼叫 Token 數: Varies by tool
費用: See repo README for pricing details
提示: Cache tool results and avoid repeated identical calls.

安全

權限、密鑰、影響範圍

憑證儲存： Use environment variables; never commit secrets

資料出站： Tool calls go to the provider's API as documented

故障排查

常見錯誤與修復

rule too strict

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

驗證： agnix check --explain <rule-id>

LSP doesn't activate

Make sure the editor extension matches your agnix CLI version.

驗證： agnix --version vs extension version

替代方案

Agnix (Agent Config Linter) 對比其他方案

替代方案	何時用它替代	權衡
Hand-rolled YAML linters	You only need one format	Won't catch cross-file issues

Agnix (Agent Config Linter)