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.
git 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/commands/deepaksinghcs14/deadeye-cc/deadeye-status)<a href="https://agentmods.dev/commands/deepaksinghcs14/deadeye-cc/deadeye-status"><img src="https://agentmods.dev/badge/commands/deepaksinghcs14/deadeye-cc/deadeye-status.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.00012 | $0.00305 |
| Opus 5 | $0.00006 | $0.00152 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
deadeye-status 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 8d 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.
What it actually says
Run deadeye status. If that reports "command not found", it's very likely
just not on PATH -- deadeye never adds itself to PATH, it only resolves its
own binary internally for hook invocations. Before concluding it's missing,
retry with the self-bootstrap install path directly:
~/.deadeye/bin/deadeye status. Only if that also fails is it genuinely not
bootstrapped yet.
Present the output to the user, organized under these headings: Modes
(per-axis advise/enforce/off), Kill switches (flag any that are OFF),
Catalog (tier table, source, build date -- flag if stale), Daemon
(up/down), Log (path and record count). If the output includes a
CLAUDE_EFFORT note, surface it prominently -- it means the effort axis is
currently inert for this session, a real constraint, not decoration.
If both invocations genuinely fail, tell the user the binary hasn't been
bootstrapped yet: it self-installs on first hook invocation, so running any
tool once in this session and then retrying /deadeye-status should resolve
it. Do not attempt to install it yourself.
Do not editorialize beyond what the output shows -- this command reports state, it doesn't take action.
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.
- 8d ago First seen · 27 lines · 12 tokens per session scan A 61a254c50aeb
deadeye-status is a command published in the GitHub repository deepaksinghcs14/deadeye-cc (5 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 305 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 commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
doctor
Check the Modellix CLI install, credential resolution, API connectivity, and balance.