AI Agent Config Analyzer

Optimize your CLAUDE.md & AGENTS.md for better instruction following

🔒

100% Client-Side Processing — Your Data Never Leaves Your Browser

This tool runs entirely in your browser using JavaScript. No data is sent to any server.

  • No uploads: Your config content is never transmitted anywhere
  • No tracking: No analytics, cookies, or telemetry
  • No storage: Nothing is saved — refresh the page and it's gone
  • Open analysis: Token counting uses the cl100k_base tokenizer (same as Claude)
Your Config File
How Analysis Works: All processing happens in your browser: tokenization via js-tiktoken (cl100k_base encoding), regex pattern matching for best practices, and structure analysis via markdown parsing. Zero network requests are made during analysis.
Analysis Results

Paste your CLAUDE.md or AGENTS.md content

Checks based on official best practices from Anthropic, OpenAI, Google & community guidelines

Best Practices Verified

📏 Optimal Length

LLMs reliably follow ~150-200 instructions. Keep files under 300 lines and ~1500-2500 tokens for best adherence.

Target: <300 lines, <2500 tokens

🏗️ Structure

Use clear markdown headers. Include: Commands, Code Style, Architecture, Testing. Avoid code style rules (use linters instead).

## Commands | ## Architecture | ## Testing

🔐 Security

Never include API keys, passwords, or secrets. Use environment variables and .gitignore for sensitive data.

❌ api_key = "sk-..." | ✓ Use $API_KEY

📦 Modularity

Use @imports for large configs. Create separate files for different concerns. Max 5 levels of nesting.

@./docs/conventions.md

⚡ Emphasis

Use IMPORTANT, YOU MUST, NEVER for critical instructions. But don't overuse — dilutes priority signals.

IMPORTANT: Always run tests before commit

🎯 Relevance

Only include universally applicable instructions. Irrelevant context gets ignored. Be specific to your project.

Focus on YOUR project's actual needs