dos-statslisted

# dos-stats ��� read the kernel's own activity log > **The DOS hooks judge your agents from non-forgeable evidence. This skill turns > that lens on the kernel itself.** Every time a hook fires (before a tool call, after > a read, on a stop), the bundled native `dos-hook` binary writes ONE line to a > durable log describing what it decided. This skill folds that log into a report you > read. It is the binary's own dogfood: the kernel emits evidence about its own > adjudication, the same way it demands evidence from the agents it judges (docs/276). ## What writes the log (so the numbers mean something) The plugin's hooks call the bundled `dos-hook` binary on every tool call. On each call the binary appends one record to `.dos/metrics/observations.jsonl` under this workspace — the verb it ran, the decision it reached, the reason class, the dialect, the exit code, how long it took. The log is **append-only and local**; nothing reads it back until you run this. It is on by default and opt-OUT with `DOS_HOOK_METRICS=0`. ## Step 1 — Fold the log into a report The binary lives in the plugin bundle, so call it by its bundle path (the same launcher the hooks use picks the right binary for your machine): ```bash "${CLAUDE_PLUGIN_ROOT}/bin/dos-hook" stats --workspace . ``` A populated run looks like this: ``` dos-hook stats — /your/project observations 4 tool calls 3 adjudicated — 2 passed untouched (66.7%), 1 intervened (33.3%) by verb posttool=1 pretool=3 b