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-helpgit 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-help)<a href="https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-help"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-help.svg" alt="Measured on agentmods" 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.00015 | $0.00814 |
| Opus 5 | $0.00008 | $0.00407 |
| Sonnet 5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
deadeye-help 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deadeye Help
Present this reference card, formatted cleanly:
Coder mode
| Level | What it does |
|---|---|
spotter |
Builds what's asked, names the leaner alternative in one line |
marksman |
The lean-first ladder enforced. Default. |
sniper |
Maximum minimalism — one-liners, challenges the requirement itself |
- Switch:
/deadeye-coder spotter|marksman|sniper|off - Report current:
/deadeye-coder - Persist a default for new sessions:
/deadeye-coder default <level>(writes deadeye's own~/.deadeye/config.json, never Claude's settings) - Turn off mid-session: say exactly
normal modeorstop coder
Commands
| Command | What it does |
|---|---|
/deadeye-status |
Modes, coder level, kill switches, catalog, daemon health |
/deadeye-config |
View or change any setting from chat (or just say what to change) |
/deadeye-route [task] |
Dry-run the routing decision with full reasoning |
/deadeye-stats [savings|context] |
Decision-log reports: measured impact (default), token savings, per-session context breakdown |
/deadeye-coder [level] |
Switch/report the coder persona level |
/deadeye-mute [off] |
Session-scoped mute for advisories/nags (rewrites stay on) |
/deadeye-review [--repo] |
Four-lens self-review of the working diff, or the whole repo with --repo -- the pre-PR version of /deadeye-pr |
/deadeye-guard |
Security review of the current diff -- full OWASP-mapped coverage (Top 10:2025, API Security Top 10 2023, LLM Top 10:2025), deps |
/deadeye-vapt |
Whole-service pen-test/VAPT pass -- full OWASP Top 10:2025/API Security Top 10 2023/LLM Top 10:2025 coverage |
/deadeye-pr [<PR>] [--post] |
PR review across four lenses -- over-engineering, correctness, performance, security |
/deadeye-debt |
Ledger of deadeye: shortcut markers |
/deadeye-help |
This card |
CLI-only: deadeye lessons [reset] inspects/clears the recorded routing
outcomes that bias future decisions. deadeye update updates the managed
binary directly (sha256-verified, atomic) — for Codex-only installs.
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 52e658c8722b
- 8d ago First seen · 64 lines · 15 tokens per session scan A aff91f82ae08
deadeye-help is a skill published in the GitHub repository deepaksinghcs14/deadeye-cc (5 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 814 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-08-31.
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…
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.
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.
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.