Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add deepaksinghcs14/deadeye-cc --skill deadeye-configgit clone --depth 1 https://github.com/deepaksinghcs14/deadeye-ccWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-config)<a href="https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-config"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-config"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.00685 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
deadeye-config scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 setDEADEYE=offin their shell (or config a specific axis tooff). - Changes to
default_leveland 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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago Changed · +4 lines 673db31c42e2
- 5d ago First seen · 60 lines · 19 tokens per session scan A 3b75c571e30f
deadeye-config is a skill published in the GitHub repository deepaksinghcs14/deadeye-cc (5 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 685 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.