Run the whole catalog — plus your own private, linted briefs — inside your org: your own deployment, your own slash commands, standing audits on a cron. Everything below already exists in the open repo; the offer is having it set up, extended with your briefs, and supported for you.
Nothing here is vaporware — each piece is live in the public repo today and MIT-licensed. A Teams engagement assembles them around your org.
GOAL_PROMPTS_BASE=https://audits.your-co.internal python3 build.py — the site, raw endpoints, conductors, and catalog.json all point at your internal deployment. Nothing your briefs touch leaves your infra.BASE=… sh install), the Claude Code plugin, the MCP server, and the skills tree — the same one-paste flow, pointed at your catalog.run-brief.example.yml ↗ wired into your repos: a scheduled brief runs on a cron and files its report as an issue — audits as an appointment, not a memory.A setup engagement plus an optional support retainer — scoped per org, priced flat, nothing metered. Pricing is on request via the partnership contact; the project is young and every engagement is scoped individually.
For scale: adjacent automated-review products price per seat — CodeRabbit’s paid tiers run about $24–$48 per user per month on their published plans. The GitHub Action above already delivers a standing audit at $0; what an engagement buys is the implementation and your own private content, once.