Claude Code linter comparison

    AgentLint vs cclint.

    cclint is a Claude Code project-file linter for agents, commands, settings, and documentation conventions. AgentLint is an agent harness linter for CLAUDE.md, AGENTS.md, .cursor/rules, CI, and hooks, with 33 evidence-backed checks.

    01 / Feature comparison

    Similar neighborhood.
    Different job.

    Both tools help Claude Code users tighten project context. The main distinction is whether you want Claude Code file validation or a broader audit of the harness that multiple coding agents read.

    DimensioncclintAgentLint
    Primary scopeClaude Code project files: agent definitions, slash commands, settings, and documentation files such as CLAUDE.md and AGENTS.md.The repo harness: CLAUDE.md, AGENTS.md, .cursor/rules, GitHub Copilot instructions, CI, hooks, .gitignore, and continuity files.
    Check modelSchema and structure validation against Claude Code file conventions, with support for custom Zod schema extensions.33 evidence-backed harness checks covering findability, instruction quality, workability, safety, and continuity.
    Reasoning citationRules are tied to Claude Code specifications and project-file conventions; custom schemas can add local policy.Each check is written against a cited primary source, such as prompt-history data, runtime behavior, or published research.
    Language coverageA Node CLI for Claude Code configuration and Markdown-style project files, not a general source-code language linter.Language-agnostic repo audit because it inspects the files agents read and the automation they trigger.
    Output formatConsole output plus JSON and Markdown report options for CI or review workflows.Score, fix plan, CLI output, and report-oriented workflows designed to show what changed in the harness.
    IntegrationCLI-first, with CI-friendly options such as quiet mode, report files, and configurable failure thresholds.CLI and CI oriented, with a Claude Code plugin flow for interactive scan-fix-report work.
    Fix behaviorBest treated as validation and reporting unless your local workflow layers fixes on top.Audits, scores, and can guide or apply targeted fixes for harness issues it understands.
    LicenseMIT, per the upstream repository badge and license metadata.MIT, matching the AgentLint repository and site footer.
    02 / When to pick which

    Pick cclint for Claude Code file validation.

    cclint is the better fit when your immediate job is checking Claude Code project files: agent frontmatter, command definitions, hook settings, context-file structure, and custom schema rules for one Claude Code setup.

    Pick AgentLint for full-harness coverage.

    AgentLint is the better fit when the problem is broader than one tool's file schema: stale instructions, unresolved references, weak CI, unsafe hooks, missing handoff context, or rules shared by Claude Code, Cursor, and Codex.

    Install AgentLint when you need the harness audit.

    Use cclint at https://github.com/carlrannaberg/cclint when you want Claude Code project-file linting. Use AgentLint when you want 33 evidence-backed checks across the repo harness.

    Install AgentLint