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/Bitmia-ai/RedEyeWrote 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/bitmia-ai/redeye/log)<a href="https://agentmods.dev/commands/bitmia-ai/redeye/log"><img src="https://agentmods.dev/badge/commands/bitmia-ai/redeye/log/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/commands/bitmia-ai/redeye/log"><img src="https://agentmods.dev/badge/commands/bitmia-ai/redeye/log.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.00004 | $0.00092 |
| Opus 5.5 | $0.00002 | $0.00037 |
| Sonnet 5.5 | $0.00001 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
log 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 1mo 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
Read .redeye/changelog.md from the project root.
If an argument was provided, use it as the number of entries to show. Default: 5.
Show the last N entries from .redeye/changelog.md, formatted clearly.
If the file is empty or has no entries, say: "No iterations completed yet. Run /redeye:start to begin."
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.
- 1mo ago First seen · 13 lines · 4 tokens per session scan A 3ef77278a969
log is a command published in the GitHub repository Bitmia-ai/RedEye (6 stars, last pushed 4mo ago), licensed MIT. It adds 4 tokens to every session and 92 once invoked, about $0.0000 per session on Opus 5.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
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
address
Answer reviewer comments on YOUR open PR — categorize unresolved threads, push fixes, and post replies. Workspace-aware across linked PRs.
release
Cut a semver release for the current repo — bump computed from conventional commits, evidence preview, tag + GitHub release.
start
Start a feature — set up an isolated worktree, draft the plan, and write the first failing test before any production code. --jira links a ticket and informs the branch name. Workspace-aware.
verify-change
A command that starts a separate, non-interactive Claude session to inspect an autopilot repository’s current Git changes.
ship
Finalize and open the PR — verifies tests, presents commit/branch/PR options, executes the chosen path, with a soft LOC size-budget gate. Last command before review; adds a Jira Resolves trailer when bound. Workspace-aware.