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 commands/mirnoorata/codexa/codexa-impactgit clone --depth 1 https://github.com/mirnoorata/codexaWhat 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 | $0.00018 | $0.00141 |
| Opus 5 | $0.00009 | $0.00071 |
| Sonnet 5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
codexa-impact 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 2d 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
Show Codexa impact evidence. With an argument, query impact for that file or
symbol. Without an argument, show diff-impact for the current dirty tree.
Relationship-backed results may include edge evidence ids, confidence labels,
stale/degraded flags, and structured next Codexa tools for symbol context,
change planning, or targeted tests.
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/impact.sh" "$ARGUMENTS"
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.
- 2d ago First seen · 15 lines · 18 tokens per session scan A b8f43f886f47
codexa-impact is a command published in the GitHub repository mirnoorata/codexa (2 stars, last pushed 29d ago), licensed MIT. It adds 18 tokens to every session and 141 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
rb-setup
First-time setup. Configure the LLM API key, or a no-API-key local host runner (Codex / Trae / Claude / any headless CLI) that RepoBrain uses for codebase Q&A and refresh. / 首次 setup，配置 RepoBrain 代码问答与 refresh 所需的 LLM API key，或无需 API key 的本地 host runner（Codex / Trae / Claude / 任意无头 CLI）。.
export
Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.
search
Search the Repowise wiki using natural language, full-text, or symbol search.
execute-parallel
Spawn N concurrent /ai-sdlc execute sessions in tmux panes (max 5). Reads the dispatch-ready frontier, presents top N candidates, asks operator to confirm, then fires one tmux window per task. Coordination via .ai-sdlc/dispatch/sessions/. Resource-gated: refuses if available memory = ncpu. AISDLC-462.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
spec
Turn an objective into a spec and implementable tasks.