Free · Agent Readiness Check
Find out what your repository teaches its agents.
Sign in with GitHub, pick a repository, and we will email you a short scored report on how your repository guides its AI coding agents — a sample slice of the full Post Code consultation.
No write access. Uninstall any time.
What we look at
One category from the full consultation: the rules your repository teaches every agent, prompt, and contributor before they touch a line of code.
- AGENTS.md or CLAUDE.md exists, stays current, and matches the codebase.
- Naming, folder structure, and import conventions are written down.
- Forbidden patterns are written down with their reasons.
- The verification commands the agent must run are listed and accurate.
- Hierarchical instruction files cover sub-packages and feature areas.
- Per-tool instruction files stay consistent with one canonical source.
- The constitution stays small and loads deeper guidance on demand.
- Safety-critical rules are mechanically enforced, not just written down.
- Constitution changes are validated against observed agent behavior.
Categories beyond agent readiness — architecture, testing, CI/CD, security, observability — are part of the full consultation rather than this check.
What we do — and never do — with your code
We use your code for one thing only: producing your audit. We pull your repository into memory, score it, and discard it the moment the audit finishes — your source is never written to disk, never stored, never used to train models, and never sold.
The only thing we keep from your repository is the report we generate for you. Read our Privacy Policy for how we handle your data.
Read-only access
We request read access to your repository’s contents and metadata — nothing more. We can’t modify, write to, or open anything else in your account.
Used only for your audit
Your files are read for one purpose: scoring this audit. They’re never repurposed, never used to train models, and never sold.
Nothing is stored
We read your repository into memory, score it, and discard it the moment the audit finishes. Your source code is never written to disk, and access tokens are short-lived — never kept.
The report, kept 100 days
We keep the report we generate for you for 100 days, then delete it — along with the email and metadata we need to deliver and operate the audit.