I built a small CLI tool called Charter that audits a repository and gives it a deterministic 0–100 readiness score for AI coding agents. The idea came from a pattern I kept seeing: coding agents usually fail less because the model is “bad” and more because the repo gives them a bad environment to work in. Missing context. No AGENTS.md. Unpinned tools. Unsafe config. Secrets sitting where an agent can read them. No clear test path. CI that is hard to reason about. The agent still tries to help, but it is basically landing in a repo that was never prepared for it. Charter checks things like: repo context secrets MCP safety agent configuration environment setup CI testing autonomy governance It runs fully offline, makes no network calls, and does not use an LLM for scoring. Same repo, same score, every time. Basic usage: brew install use-charter/tap/charter charter doctor or: go install go.use-charter.dev/charter/cmd/charter@latest charter doctor The output gives you a score, rule-by-rule findings, and suggested fixes. It can also emit SARIF for GitHub Code Scanning and run in CI with a score threshold. GitHub: https://github.com/use-charter/charter Longer write-up: https://use-charter.dev/blog/introducing-charter/ I’d love feedback from CLI/tooling folks especially: does the rule set make sense, what feels too strict, and what checks would you expect in a tool like this?   submitted by   /u/tashfiq61 [link]   [comments]