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-sweepgit 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-sweep)<a href="https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-sweep"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-sweep/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-sweep"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-sweep.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.00071 | $0.03918 |
| Opus 5 | $0.00036 | $0.01959 |
| Sonnet 5 | $0.00014 | $0.00784 |
| Haiku 4.5 | $0.00007 | $0.00392 |
Grade A, and why
deadeye-sweep 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.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deadeye Sweep
/deadeye-review, /deadeye-pr, and /deadeye-guard all end the same way:
"Findings are a LIST. Do not apply them unless asked." Typing /deadeye-sweep
IS that ask. It runs the review, audits each finding's premise, applies the
ones that are 🔴/🟠 and in reach, proves the tree still builds, then
re-scans the changed code and repeats until a pass comes back clean.
Sweep does not reimplement scanning — it invokes the existing skills and consumes their printed findings. Coder mode stays active throughout: the fixes it writes follow the lean-first ladder, not a patch bolted at the line the finding named.
Scope
- default — the working diff. Scan:
/deadeye-review, then/deadeye-guard. --pr [<PR>]— that PR, or the current branch's PR with none given. Scan:/deadeye-pr <PR>, then/deadeye-guard, then the PR's own open review comment threads (see "PR review comments" below). If the current branch isn't the PR's head branch, ask beforegh pr checkout <PR>— before pass 1 does anything, since every fix that follows is applied locally to that branch.--repo— the whole repository. Scan:/deadeye-review --repoonly —/deadeye-guardhas no whole-repo mode, and--repoalready runs the security lens plus native dependency auditors.- A bare integer lowers the pass cap (default: loop until clean, hard cap
5) — e.g.
/deadeye-sweep --repo 2. The integer right after--pris the PR number; any other bare integer is the cap. --commit— commit each pass that verifies green. Off by default. Never pushes on its own; see "PR handoff" below.--all— lowers the severity floor to include 🟡 medium and ⚪ nits (see "What gets fixed"). Off by default — the unattended default stays 🔴/🟠 only. The reach gate still applies either way;--allwidens which severities qualify, not how far a fix is allowed to reach.
Empty diff (nothing changed or staged): say so plainly and stop — do not substitute a different scope. Not a git repo: stop, sweep needs a restore point it can't build without one.
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.
- today First seen · 313 lines · 71 tokens per session scan A 428dea8a405e
deadeye-sweep is a skill published in the GitHub repository deepaksinghcs14/deadeye-cc (5 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 3,918 once invoked, about $0.0004 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-12.
Other skills, from other repositories
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
vet
Thorough codebase investigation that finds and fixes real problems. Maps architecture, scans every layer (structural, correctness, security, reliability, performance, hygiene), prioritized report with evidence, fix plan, executes collaboratively. A senior engineer doing a full review with authority to fix. Use when…
daily-prevention
Use this skill to help a developer keep day-to-day code simple, maintainable, and robust — through automatable prevention (linters, type checkers, static analysis, and — for what static analysis structurally can't catch — AI-assisted review skills) rather than after-the-fact fixes. Trigger on "how do I keep this…
verify-simplify
A final code-cleanup workflow that runs at the end of verification. It removes repeated or unnecessary logic after the other verification steps are complete.
phx-challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
lsp-investigate
Investigate code using LSP tools. Register a project, then use definitions, references, call hierarchies, type hierarchies, hover, and diagnostics to understand code structure, trace bugs, and assess change impact.