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/aurora-neuro/aurora-agent/explaingit clone --depth 1 https://github.com/AURORA-NEURO/aurora-agentWrote 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/aurora-neuro/aurora-agent/explain)<a href="https://agentmods.dev/commands/aurora-neuro/aurora-agent/explain"><img src="https://agentmods.dev/badge/commands/aurora-neuro/aurora-agent/explain.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 | $0.00026 | $0.00298 |
| Opus 5 | $0.00013 | $0.00149 |
| Sonnet 5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
explain 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 4d 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
Explain the FIBER compile plan for a world and query, faithfully.
- Resolve the aurora-agent checkout (
$AURORA_AGENT_ROOT→~/aurora-agent→~/bioprism); CLI at<root>/target/release/bioprism(.exe). - Defaults if
$ARGUMENTSis empty: worldfixtures/fiber-v0.1/radiogenomic_world.json, queryfixtures/fiber-v0.1/leakage_query.json. - Run from the checkout root:
bioprism --json context explain --world <world> --query <query> - Report ALL of: the passes that ran (name, retained counts, notes), the
passes that did NOT run, each with its stated reason, verbatim — this is
the honest-labelling core of the output, never omit it — the selection
ratios, the omission manifest (reason, influence class, count, bound), and
the sufficiency-claim flag. Exit code 0 = ok; interpret failures with the
retryability matrix (
error.retryabilityin the JSON envelope).
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.
- 4d ago First seen · 21 lines · 26 tokens per session scan A e5d05172dc57
explain is a command published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 298 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
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
10-optimization-finalization
Comprehensive Optimization: Multi-agent optimization, PRD improvement, documentation consolidation, and production-ready finalization.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.