Skip to content
Back to skills

Deadeye Config

ASecurity

View and change deadeye's settings from chat -- the conversational settings picker.

  • 5 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsshellgitsecurity

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add deepaksinghcs14/deadeye-cc --skill deadeye-config --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Deadeye Config?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Deadeye Config
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/deepaksinghcs14-deadeye-config/badge)](https://www.skillsdirectory.com/skills/deepaksinghcs14-deadeye-config)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: deadeye-config
description: View and change deadeye's settings from chat -- the conversational settings picker.
license: MIT
argument-hint: "[<what to change>]"
---

# Deadeye Config

Change deadeye's settings without anyone editing JSON. You are the selector.

Run `deadeye config list` to see every tunable key, its current value, and its
allowed values. If that reports "command not found", it's just not on PATH --
retry `~/.deadeye/bin/deadeye config list`. Present the result to the user as a
short list. For what a key actually DOES, point them at
https://deepaksinghcs14.github.io/deadeye-cc/settings.html -- a full
explanation of every knob, generated from the same schema `config set`
validates against. Don't retype those explanations from memory; link it.

- If the user already said what they want ("turn off the plan gate", "coder to
  sniper", "make reviews stricter"), map it to the right key/value and apply it
  directly -- don't make them pick from a menu.
- Otherwise, ask which setting to change, then which value.

Apply a change with exactly:

    deadeye config set <key> <value>

It validates against the schema and writes `~/.deadeye/config.json`, preserving
every other setting. Show the user the confirmation line it prints.

Keys and allowed values (authoritative -- never invent others):

| Key | Values |
|---|---|
| `mode.routing` | off · advise · enforce |
| `mode.effort` | off · advise |
| `mode.preprocess` | off · on |
| `mode.plan_gate` | off · soft · hard |
| `mode.workflow_hint` | off · on |
| `mode.codemap` | off · on |
| `mode.update_check` | off · on |
| `mode.routing_judge` | off · on |
| `mode.catalog_check` | off · on |
| `coder.default_level` | off · spotter · marksman · sniper |
| `coder.security` | off · advise · ask |
| `coder.security_osv` | true · false |
| `security.exfil` | off · advise · ask |

Also settable (free-form): `coder.subagent_matcher` (regex),
`downshift_threshold` (0-1), `injection_budget_tokens` /
`coder.injection_budget_tokens` (int), `plan_gate.min_files` (int).

## Boundaries

- Only ever run `deadeye config get|set|list`. Never hand-edit the JSON, and
  never set a key or value not listed above.
- Kill switches (`DEADEYE=off`, `DEADEYE_PREPROCESS/GATE/CODER=off`) are ENV
  vars, not config keys. If the user wants everything off, tell them to set
  `DEADEYE=off` in their shell (or config a specific axis to `off`).
- Changes to `default_level` and other defaults take effect next session; the
  live coder level for THIS session changes with `/deadeye-coder <level>`.
- For the full list of commands, point the user at `/deadeye-help`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.