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/verifygit 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/verify)<a href="https://agentmods.dev/commands/aurora-neuro/aurora-agent/verify"><img src="https://agentmods.dev/badge/commands/aurora-neuro/aurora-agent/verify.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.00018 | $0.00243 |
| Opus 5 | $0.00009 | $0.00121 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
verify 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
Verify a context certificate.
- Resolve the aurora-agent checkout (
$AURORA_AGENT_ROOT→~/aurora-agent→~/bioprism); CLI at<root>/target/release/bioprism(.exe). $ARGUMENTSmust name a certificate JSON path (relative to the root). If none was given, ask which certificate to verify — or compile one first withcontext compile --certificate-out <path>.- Run from the checkout root:
bioprism --json context verify --certificate <path> - Report the
verificationstring verbatim ("digest verifies" or the failure text) plus the schema version. Exit 0 = the digest verifies; exit 1 = assertion_failed is the honest "it does not verify" verdict, not a tool error. Certificates are verifiable without the engine that produced them — that independence is the design point worth mentioning when relevant.
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 · 20 lines · 18 tokens per session scan A 3c643420b111
verify is a command published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 243 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.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.