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
호출당 토큰: 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)