Auto-invokedCommand
deadeye-mute
Mute deadeye's advisories, plan-gate nags, and workflow hints for this session
@deepaksinghcs14View CommandDevelopment
/deadeye-status
Modes, coder level, kill switches, catalog, daemon health
Install
> /plugin marketplace add deepaksinghcs14/deadeye-cc > /plugin install deadeye@deadeye
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/deadeye-status
Context preview
What this command does when you run it.
Modes, coder level, kill switches, catalog, daemon health
Command definition
deadeye-status.mddescription: Modes, coder level, kill switches, catalog, daemon health
allowed-tools: Bash(deadeye status), Bash(~/.deadeye/bin/deadeye status), Bash(deadeye doctor), Bash(~/.deadeye/bin/deadeye doctor)
Run `deadeye status`. If that reports "command not found", it's very likely just not on PATH -- deadeye never adds itself to PATH, it only resolves its own binary internally for hook invocations. Before concluding it's missing, retry with the self-bootstrap install path directly: `~/.deadeye/bin/deadeye status`. Only if that also fails is it genuinely not bootstrapped yet.
Present the output to the user, organized under these headings: **Modes** (per-axis advise/enforce/off), **Kill switches** (flag any that are OFF), **Catalog** (tier table, source, build date -- flag if stale), **Daemon** (up/down), **Log** (path and record count). If the output includes a `CLAUDE_EFFORT` note, surface it prominently -- it means the effort axis is currently inert for this session, a real constraint, not decoration.
If both invocations genuinely fail, tell the user the binary hasn't been bootstrapped yet: it self-installs on first hook invocation, so running any tool once in this session and then retrying `/deadeye-status` should resolve it. Do not attempt to install it yourself.
Do not editorialize beyond what the output shows -- this command reports state, it doesn't take action.
If the user's question is "is it WORKING" rather than "what is it set to" -- nothing seems to be happening, an advisory never appears, a setting seems ignored -- run `deadeye doctor` instead and present that. `status` shows configuration, which looks identical whether the plumbing under it is healthy or broken; doctor checks the plumbing (binary resolution, state-dir permissions, whether config.json parses, socket, daemon, whether the routing judge can reach `claude`, hook-manifest coverage) and prints the fix for each failure. Same PATH fallback applies.
Read more
description: Modes, coder level, kill switches, catalog, daemon health allowed-tools: Bash(deadeye status), Bash(~/.deadeye/bin/deadeye status), Bash(deadeye doctor), Bash(~/.deadeye/bin/deadeye doctor)
Run `deadeye status`. If that reports "command not found", it's very likely just not on PATH -- deadeye never adds itself to PATH, it only resolves its own binary internally for hook invocations. Before concluding it's missing, retry with the self-bootstrap install path directly: `~/.deadeye/bin/deadeye status`. Only if that also fails is it genuinely not bootstrapped yet.
Present the output to the user, organized under these headings: **Modes** (per-axis advise/enforce/off), **Kill switches** (flag any that are OFF), **Catalog** (tier table, source, build date -- flag if stale), **Daemon** (up/down), **Log** (path and record count). If the output includes a `CLAUDE_EFFORT` note, surface it prominently -- it means the effort axis is currently inert for this session, a real constraint, not decoration.
If both invocations genuinely fail, tell the user the binary hasn't been bootstrapped yet: it self-installs on first hook invocation, so running any tool once in this session and then retrying `/deadeye-status` should resolve it. Do not attempt to install it yourself.
Do not editorialize beyond what the output shows -- this command reports state, it doesn't take action.
If the user's question is "is it WORKING" rather than "what is it set to" -- nothing seems to be happening, an advisory never appears, a setting seems ignored -- run `deadeye doctor` instead and present that. `status` shows configuration, which looks identical whether the plumbing under it is healthy or broken; doctor checks the plumbing (binary resolution, state-dir permissions, whether config.json parses, socket, daemon, whether the routing judge can reach `claude`, hook-manifest coverage) and prints the fix for each failure. Same PATH fallback applies.
Ships withdeadeye
Claude Code plugin that fits the model, effort, and context to each task — fewer tokens, same quality. Deterministic policy kernel in the hooks; every number it reports is measured, not estimated.
Get the whole plugin, auto-invoked
Other commands on deadeye.
@deepaksinghcs14View CommandAuto-invokedCommand