Free
$0
- Rules editor & audit viewer
- Default blocklist & git hooks
- Open-source CLI (editable install)
DestructGuard
DestructGuard intercepts force pushes, hard resets, recursive deletes, and database drops before execution — with a human checkpoint and durable audit trail. Get Pro Pack for 30s to protected offline: curated rulesets + PRO-EXTRAS. 30-second unzip vs 15-minute clone + pip install. Team subscribers get a monthly rules changelog, team policy preset sync, and premium feed updates via Shopify.
30s after purchase: instant ZIP • full CLI + 3 rulesets • PRO-EXTRAS • templates • run `destructguard doctor` and protected.
Instant access • 30s to protected • Buy once. Own forever. Get Pro Pack — $9 • instant • own guard. Protect now — $9 • instant • 30s to guarded CLI
Unzip → doctor → block a force-push (exit 2)
Coding agents run with the same privileges as you. One bad suggestion — git push --force, DROP DATABASE, rm -rf / — can wipe history, destroy production data, or brick a machine. There is no undo button after the subprocess starts. Documented agent incidents show these exact patterns causing real data loss.
Every guard invocation appends one JSONL line. Example decisions from the audit log:
| Timestamp | Decision | Command | Rule |
|---|---|---|---|
| 2026-06-11T10:05:30.000Z | denied | kubectl delete pods --all -n prod | kubectl-delete |
| 2026-06-10T14:22:01.123Z | denied | git push --force origin main | git-force-push |
| 2026-06-09T09:15:00.000Z | approved | git push --force | git-force-push |
| 2026-06-08T11:00:00.000Z | denied | rm -rf / | rm-rf-root |
| 2026-06-07T14:20:00.000Z | approved | npm run build | — |
Explicit outcomes (risk → result from demo entries):
rm -rf / suggested by agent in root. Before: executes, root wiped, no record. Outcome: prevented — rule matched, denied (exit 2), JSONL audit written, subprocess never started, data safe.git push --force on feature branch. Before: remote history rewritten, no audit. Outcome: denied (git-force-push), exit 2, no subprocess spawned.Teams already pay for this. Documented incidents:
rm -rf agent incidents (prompts missed path expansion). Sourcegit push --force / reset --hard in claude-code and codex.One force-push or rm -rf recovery costs a team days of work. Documented adjacent contracts run $5500/yr; this $9 pack pays for itself on the first real block (exit 2).
Exclusive to Pro Pack buyers
shopify theme push --force, terraform destroy -target=module.prod (high-blast-radius agent risk from paid patterns)This level of production pattern + playbook ships only with the paid Pro Pack. Free tools and OSS snapshot do not include paid-only PRO-EXTRAS.md or the full rollout guide.
Team rollout framework (Pro Pack only)
default.json for individuals; strict.json for shared/staging/agent sandboxes; ci-pipeline.json for CI runners (non-interactive).This rollout playbook is Pro Pack only. Free tools and OSS snapshot do not include TEAM-POLICY-GUIDE.md.
~/.destructguard/rules.json.approve to proceed or abort to deny (exit code 2, no subprocess spawned).~/.destructguard/audit.jsonl.Get the CLI, wire git hooks, and wrap your agent shell — under five minutes from a fresh clone.
Editable install from the repo root, or follow Pro Pack INSTALL.md for the self-contained bundle.
pip install -e ".[dev]"Scans staged diffs on commit and delegates force-push attempts to the guard.
destructguard install-hooksPrefix every agent-spawned command so blocklisted argv is caught before exec.
destructguard guard -- <command>Drop-in agent snippets: copy templates/cursorrules-snippet.txt into your agent rules, or source templates/shell-wrap.sh for a dg() bash wrapper (Git Bash or WSL on Windows). Team subscribers: copy templates/github-rules-update.yml into .github/workflows/ and set the DESTRUCTGUARD_FEED_TOKEN repository secret to your Shopify feed token.
Already bought the Pro Pack? Team keeps your blocklists current with a monthly premium rules feed, changelog previews via destructguard rules update --check, and team policy preset sync — plus a personal feed token for destructguard rules update.
Why the Pro Pack over free tools + OSS? Free tools = browser playground. OSS = clone + pip + edit from source. Pro Pack = curated offline bundle + exclusives + 30s unzip + playbook + no setup time.
You own the exact CLI + rules + guides forever. No login, no hosted account, no subscription to use what you bought.
$0
Recommended
$9one-time
One force-push or rm -rf recovery costs a team days of work. $9 pays for itself on the first real block (exit 2) vs documented $5500/yr contracts.
Guard my repo now — $9 one-time30-day satisfaction guarantee via seller
Unzip → doctor → block a force-push (exit 2)
You own the exact CLI + rules + guides forever. No login, no hosted account, no subscription to use what you bought.
60 seconds after purchase — first prevent:
destructguard doctor (or pip install -e ".[dev]" in the cli folder + doctor).destructguard guard -- git push --force (or any blocked command) and see deny (exit 2).30s after purchase — what you receive (scannable in 2 minutes):
30s after purchase: instant ZIP • full CLI + 3 rulesets • PRO-EXTRAS • templates • run `destructguard doctor` and protected. Get Pro Pack — $9 one-time • 30s to protected. Get instant guard — $9 one-time • 30s to protected
30-second unzip vs 15-minute clone + pip • pays for itself on first prevent • Instant ZIP download • curated rules + playbook + PRO-EXTRAS • upgrade path to Team included
Upgrade to Team for monthly feed + preset sync
$15/mo via Shopify
Billed through Shopify; cancel anytime. Cloud audit sync is still on the roadmap. See UPGRADE.md.