Org-level safety services — audit, training, baseline rollout and ongoing review, by the author of cc-safe-setup.
.env into git, drop a production database, or trigger unexpected billing —
and that happens no matter how careful the other nineteen people are.
This page lays out how to make safety uniform, enforced and audited across the org, with the practical patterns to get there.
.env staging, force‑push, runaway sub-agents, unexpected billing.
These are blocked with hooks, the same baseline is enforced across every repo in the org, and CI plus an audit trail keep confirming it still works.
| Typical training / hardening | This service (operational accident prevention) | |
|---|---|---|
| Focus | Learning to use it / securing the environment | Stopping dangerous operations before they run |
| Depends on | Trainee attention / following rules | Mechanical enforcement (hooks, CI, audit) |
| Pricing shape | Mainly per-seat training fees | Audit + monthly review (not per-seat) |
| Position | The on-ramp | The downstream layer for the "accidents still happen in the field" problem that always remains |
It composes with training rather than competing with it: the same diff-style enforcement that catches a weakened baseline in CI is what training alone can't give you.
The basis is real, documented incidents and on-machine verification of the hooks that stop them — for example an unauthorized transfer #46828 ($1,446), mass deletion of database tables #27063, and a secret leak that walked straight past CLAUDE.md instructions #2142. Not generalities — incidents you can trace by number, with the matching hook.
The figures below are estimates. They move with team size, number of repos and your existing setup, so start with a conversation — the actual scope and price come back in a quote. These engagements are async / remote-friendly (the audit and baseline work are delivered as artifacts and reports; training is available recorded).
Review the org's settings.json, CLAUDE.md and hook setup, and surface the gaps that lead to accidents (permission holes, secret-leak paths, deletion and billing risk). You get the remediation config and a distributable safety baseline. Delivered as a written report — no live session required.
See a sample vulnerability report → (fictional company, for illustration)
For tech leads and developers: how to operate Claude Code safely, taught through real incidents and how to prevent them, mapped onto your own workflow. Available recorded so it scales across time zones.
from ~$350 / person (varies by size & format) Recorded option · 7-module curriculumDesign the shared safety policy, the mechanism to distribute it to every repo and developer, the CI safety gate, and enforcement of the required baseline. Eliminates the drift and "forgot to add it" failures of manual distribution.
from ~$2,000 (one-off project) Deliverable: shared policy + CI workflow + rollout runbookThe core service. Ongoing hook updates, responses to newly reported incident classes, config review, and operational Q&A. Claude Code ships fast and the safety assumptions shift; training and initial setup are one-time, but the risk stays for as long as you keep using it. Priced per org's operation, not per seat.
from ~$700 / month (varies by scale) Continuous safety updates + review + auditOne-off: AI-coding adoption strategy, safety-design review, or root-cause analysis and prevention after an incident has already happened.
from ~$2,000 / day Strategy / design review / post-mortemThe core hooks stay free and MIT, always. On top of that, a per-developer monthly tier that distributes and enforces a shared policy across the org, runs it in CI, and keeps an audit trail. I'm confirming demand before building it — if it'd help your org, a 👍 or a line is enough.
~$12 / developer / month (gauging interest) Deliverable: monthly compliance report + incident-rule feed + bypass auditSee a sample monthly compliance report → (fictional company, for illustration)
Before any conversation, check where you stand with the free tools — all usable in-house as-is.
| Tool | What it does |
|---|---|
| Team Governance Scorecard | Score 8 org-level controls in 30 seconds; get a shareable card and a clear "what to fix next" list |
| Safety Scorecard (per developer) | Check the individual layer: 8 documented incidents, X/8 coverage you can screenshot |
| cc-safe-setup (free · MIT) | One command installs the core safety hooks. The individual tier stays free. |
For an inquiry or a quote, use the GitHub issue form — a short form where you pick the type and size of engagement. Don't include your company name or anything confidential; after the first contact we move to a private channel.
Inquire via the GitHub form First, score your teamAuthor of cc-safe-setup (800+ safety hooks · MIT) ~30k npm installs (cumulative) ~1,900 de-duplicated GitHub clones in the last 14 days (measured, includes automated traffic such as CI) GitHub 42★ 80k+ cumulative Qiita views on Claude Code safety & operations Designed from real, documented incidents (GitHub issues)
Figures are measured as of publication. Scope and schedule are agreed per engagement. No exaggerated promises.