Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AgentBuildersApp/eight-eyes/plugin install 8eyesWrote 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/agentbuildersapp/eight-eyes/8eyes)<a href="https://agentmods.dev/commands/agentbuildersapp/eight-eyes/8eyes"><img src="https://agentmods.dev/badge/commands/agentbuildersapp/eight-eyes/8eyes.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.00815 |
| Opus 5 | $0.00006 | $0.00407 |
| Sonnet 5 | $0.00002 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
8eyes 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 6d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
8eyes Orchestrator
The user invoked this command with: $ARGUMENTS
This command is an execution workflow, not a prompt suggestion. You MUST follow the steps below in order. Do not collapse this into a single-agent review. Do not skip the Agent tool. Do not skip progress reporting.
Required Workflow
- FIRST ACTION: run this via the Bash tool:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/collabctl.py init --objective "$ARGUMENTS"If the objective is missing, stop and ask the user for it instead of inventing one. - Immediately run:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/collabctl.py statusShow the mission ID, objective, current phase, and the planned role order. - Present the plan and WAIT for explicit user approval before spawning any subagent.
- Advance to implement, then spawn a NAMED
collab-implementersubagent via the Agent tool. When it completes:- show a phase progress summary
- show the per-role result block:
- Role:
implementer - Recommendation
- Key findings
- Role:
- Advance to test, then spawn a NAMED
collab-test-writersubagent via the Agent tool. When it completes:- show a phase progress summary
- show the per-role result block:
- Role:
test-writer - Recommendation
- Key findings
- Role:
- Advance to audit, then spawn these NAMED subagents in PARALLEL via the Agent tool:
collab-skepticcollab-securitycollab-performancecollab-accessibilityWait for all four results. After EACH role completes, show:- role name
- recommendation
- key findings After all four complete, show a combined audit progress summary.
- Advance to verify, then spawn a NAMED
collab-verifiersubagent via the Agent tool. When it completes:- show a phase progress summary
- show the per-role result block:
- Role:
verifier - Recommendation
- Key findings
- Role:
- Finish with a final summary that reports findings per role and the overall recommendation.
Looping Rule
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.
- 6d ago First seen · 94 lines · 12 tokens per session scan A e57e8b70b016
8eyes is a command published in the GitHub repository AgentBuildersApp/eight-eyes (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 815 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
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
pi-askall
Ask both Codex and Gemini the same question — get three perspectives with Claude synthesis.
pi-fact-check
Fact-check content via Gemini search + Claude verification — cross-provider claim validation.
pi-ask-gemini
Ask Gemini a question — get Google's perspective alongside Claude's.
conventions-check
Check AGENTS.md, CLAUDE.md, and the projected agent artifacts (skills, subagents, commands) against the repo's conventions.
register-plugin-asset
新しい配布 command / agent / agent-skill を plugin manifest に登録し、検証シーケンスまで実行する.