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-plangit 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.00011 | $0.00173 |
| Opus 5 | $0.00005 | $0.00086 |
| Sonnet 5 | $0.00002 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
codexa-plan 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
Save a Codexa change-plan snapshot so the post-edit review can compute drift afterward. Quote the task so it is parsed as a single argument, then list the files you intend to edit. The saved snapshot includes planned-test provenance, verification recipes, freshness, and dirty-file hashes so the later review can distinguish trusted coverage from degraded legacy or stale evidence.
Examples:
/codexa-plan "fix auth bug" src/auth.py
/codexa-plan "redesign frame header" web/src/App.tsx web/src/styles.css
!bash "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/plan.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 · 21 lines · 11 tokens per session scan A 5d439dee1991
codexa-plan is a command published in the GitHub repository mirnoorata/codexa (2 stars, last pushed 29d ago), licensed MIT. It adds 11 tokens to every session and 173 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-ask
Ask a question about the current project's codebase via the repobrain knowledge hub. / 通过 repobrain 知识库询问当前项目代码。.
rb-refresh
Rebuild the repobrain project knowledge base after significant changes. / 在重要改动后重建 repobrain 项目知识库。.
coverage
Ingest or inspect test-coverage reports — LCOV, Cobertura/Clover, or coverage.py .coverage (builds the per-test map when contexts are present).
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
triage
Score and triage an issue with the RFC-0008 admission composite (PPA + pillar breakdown). Auto-detects GitHub or Backlog.md.
detect-patterns
Analyze tool call history to detect repetitive workflow patterns and propose automations.