cm-guardian-runtime — destructive command & freeze checks
SkillAI & modelsUse when you need to check if a destructive command is blocked or run guardian freeze checks.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the cm-guardian-runtime — destructive command & freeze checks skill
What this skill tells your AI
The instructions your AI receives, as published by tody-agent/codymaster in skills/cm-guardian-runtime/SKILL.md and read by ahel’s review.
Commands
cm guardian check -- git push --force origin main # exits 1 if blocked
cm guardian path-check --file ./src/app.ts --roots src,lib
Behaviour
- Regex set for
rm -rf,DROP TABLE,git push --force,git reset --hard, pipes to shell, etc. - Prefix whitelist includes
npm run build,npm test,npx vitest. - Violations append to
.cm/guardian.log.
Investigate / debug mode
When using cm-debugging or root-cause work, treat freeze roots as mandatory: only edit inside allowed directories until the hypothesis is proven.
Config
See .cm/config.example.yaml → guardian:. Hook patterns (Cursor / Codex): docs/workflows/guardian-hooks.md (repo root).
Signals
- GitHub stars
- 52
- Forks
- 23
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
cm-guardian-runtime- Source
- github.com/tody-agent/codymaster