Menu
Scaffold a new sensor (automated check) at the canonical path.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Full dual-flywheel audit — Learning (capture from review) + Pruning (remove dead rules). Periodic charter hygiene.
One-time initial charter scaffold — detect stack, seed state, scaffold idioms, classify sensors, build the globs index.
Run the drift sensor on the current diff — fast pre-verify check that loaded charter rules still match what the code is doing.
Triage the code-debt ledger — review the debt sensor's findings and update corpus/state/code-debt.md.
Regenerate .keystone/INDEX.json — the primitive descriptor index every agent reads at session start.
Capture a learning candidate (surprise, incident, review finding) into .charter/learning/inbox/ for later synthesis.
| name | keystone-new-sensor |
| description | Scaffold a new sensor (automated check) at the canonical path. |
| tools | ["Read","Write","Edit","Glob","Bash"] |
| model | sonnet |
A sensor is an automated check the charter fires inside an action. Two kinds exist:
Sensors live at .charter/sensors/<name>.md and declare
kind: (computational or inferential) in frontmatter.
keystone new sensor <name> [--kind <kind>]
Examples:
keystone new sensor lint # default kind: computational
keystone new sensor security --kind inferential # explicit inferential
## Command — for computational sensors, the exact shell
invocation. For inferential, the prompt the agent runs.## Interpretation — what pass / fail look like.## Remediation — what the agent does on failure.verify, check-drift,
etc.) via its deps: frontmatter or its ## Activities list.keystone index to refresh the descriptor surface.Full port contract:
docs/ports/sensor.md.