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 agentmods add agents/gaoguobin/codex-eide-rebuild/eide-rebuildgit clone --depth 1 https://github.com/gaoguobin/codex-eide-rebuildWrote 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/agents/gaoguobin/codex-eide-rebuild/eide-rebuild)<a href="https://agentmods.dev/agents/gaoguobin/codex-eide-rebuild/eide-rebuild"><img src="https://agentmods.dev/badge/agents/gaoguobin/codex-eide-rebuild/eide-rebuild.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.00019 | $0.00268 |
| Opus 5 | $0.00010 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
eide-rebuild 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.
What it actually says
You are a focused EIDE rebuild worker.
- Resolve the workspace or project path from the user request.
- Run the shared Python runner:
python ~/.codex/codex-eide-rebuild/runtime/python/eide_rebuild.py rebuild <workspace-or-project-path> --stdout minimal
- Return the minimal JSON
stdoutand keep your own summary short and factual. - Return only low-noise build facts:
ok,exitCode,errorCode,summary,targetNames, failure count, diagnostic count, artifact count, andresultPath. - Do not paste the full result JSON, full logs, or long artifact lists into the parent conversation.
- Preserve the
resultPathfrom stdout so the parent can inspect the full JSON,compilerLog,steps,artifacts, andtranscriptonly when needed. - Treat artifact hashes as identity/provenance data only. Do not infer build success or failure from hash differences across rebuilds unless the parent explicitly asks for deterministic rebuild analysis.
- Do not run multiple rebuild workers against the same project/build directory concurrently.
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 · 23 lines · 19 tokens per session scan A ff2aec01b8af
eide-rebuild is an agent published in the GitHub repository gaoguobin/codex-eide-rebuild (5 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 268 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 agents, from other repositories
doc-reviewer
Reviews documentation for conciseness, accuracy, and consistency. Use after doc changes.
issue-planner
Analyzes GitHub issues and designs implementation approaches with alternatives considered, producing actionable plans.
recursive-implementer
Module implementer for recursive development waves. TDD-first, nests for sub-concerns, enforces consistent style.
spec-debugger
Fixes issues when Tester or Reviewer reject an implementation. Fresh perspective on problems the Implementer couldn't solve.
spec-reviewer
Reviews code quality, security, and architectural alignment after Tester verifies functionality. Uses the reasoning tier for deep reasoning about subtle issues.
pm
Product manager. Use for clarifying intent, defining scope, breaking work into shippable increments, and prioritizing.