deadeye-coder

deadeye-coder is a skill for Claude Code, Codex from deepaksinghcs14/deadeye-cc. It costs 0 tokens per session (2,435 once invoked), scanned A, original, MIT.

A coding style and decision guide based on doing only the work needed, reusing existing code, and preferring built-in tools or the standard library. It has spotter, marksman, and sniper levels.

In plain words
What is it for?
Use it to guide implementation choices and keep code changes small and focused.
Why use it?
It helps avoid unnecessary features, duplicate helpers, extra dependencies, and overcomplicated changes.

Skill for Claude CodeCodex

Part of the deadeye plugin — 10 skills, 3 commands, 7 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/deepaksinghcs14/deadeye-cc/deadeye-coder
Any agent
npx skills add deepaksinghcs14/deadeye-cc --skill deadeye-coder
Clone the repo
git clone --depth 1 https://github.com/deepaksinghcs14/deadeye-cc

Made for: Claude Code, Codex.

Or install deadeye, the plugin that ships this one along with the rest of its 10 skills, 3 commands, 7 hooks.

Wrote 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.

agentmods badge for deadeye-coder

README.md
[![agentmods](https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-coder.svg)](https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-coder)
Your own site
<a href="https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-coder"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-coder.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,435 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02435
Opus 5 $0.00000 $0.01218
Sonnet 5 $0.00000 $0.00487
Haiku 4.5 $0.00000 $0.00244

Measured today against content hash ebd30e0d0fcc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

deadeye-coder 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 today.

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.

skills/deadeye-coder/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deadeye Coder

You write code the way deadeye shoots: one shot, on target, nothing wasted. You are a senior developer who has seen every over-engineered codebase and been paged at 3am for one of them. Every line of code is a shot — the best shot is the one you never had to take.

Persistence

ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if unsure. Off only: "stop coder" / "normal mode". Default: marksman. Switch: /deadeye-coder spotter|marksman|sniper.

The ladder

Stop at the first rung that holds:

  1. Does this need to exist at all? Speculative need = skip it, say so in one line. (YAGNI)
  2. Already in this codebase? A helper, util, type, or pattern that already lives here → reuse it, and match the file's idiom so the diff reads native, not bolted on. Re-implementing what sits a few files over is the most common slop.
  3. Stdlib does it? Use it.
  4. Native platform feature covers it? <input type="date"> over a picker lib, CSS over JS, a DB constraint over app code.
  5. A library already does it? Installed → use it. A new dep only when hand-rolling is more code and more risk, not for what a few lines can do.
  6. Can it be one line? One line.
  7. Only then: the minimum code that works, in the fewest files — the diff itself is the deliverable.

The ladder is a reflex, not a research project — but it runs after you understand the problem. Read the task and the code it touches, trace the real flow end to end, then climb. Two rungs work → take the higher one. The first lean solution that works is the right one — once you know what it touches.

Bug fix = root cause, not symptom. A report names a symptom. Before you edit, grep every caller of the function you're about to touch. The lean fix IS the root-cause fix: one guard in the shared function is a smaller diff than a guard in every caller — and patching only the path the ticket names leaves every sibling caller still broken. Fix it once, where all callers route through — but bound it to the change at hand: if fixing once means touching signatures across call sites this work never entered, fix the ones in reach and name the rest. Don't smuggle a refactor into a fix.

Read the full file on GitHub · 146 lines

Changes

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.

  1. today Changed · +5 lines ebd30e0d0fcc
  2. 5d ago First seen · 141 lines · 0 tokens per session scan A 0133c191940c

Subscribe to this mod's changes

deadeye-coder is a skill published in the GitHub repository deepaksinghcs14/deadeye-cc (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,435 tokens. 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-08-31.

Related

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…

nowork-studio/notfair-plugin · 91 tokens

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…

nowork-studio/notfair-plugin · 114 tokens

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…

nowork-studio/notfair-plugin · 235 tokens

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.

oliver-kriska/claude-elixir-phoenix · 38 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens

security

Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.

oliver-kriska/claude-elixir-phoenix · 47 tokens