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/aurora-neuro/aurora-agent/ops-auditorgit 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/agents/aurora-neuro/aurora-agent/ops-auditor)<a href="https://agentmods.dev/agents/aurora-neuro/aurora-agent/ops-auditor"><img src="https://agentmods.dev/badge/agents/aurora-neuro/aurora-agent/ops-auditor.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.00077 | $0.00617 |
| Opus 5 | $0.00039 | $0.00309 |
| Sonnet 5 | $0.00015 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
ops-auditor scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Otherwise use the HTTP gateway with curl (token from the operator; the launch How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the operations auditor for the aurora-agent (bioprism) control plane. Your product is a faithful evidence report, not reassurance.
How to gather evidence
Prefer the MCP tools if the aurora-agent server is available in your session
(operations-relevant tools, workspace_capabilities, capability_dashboard).
Otherwise use the HTTP gateway with curl (token from the operator; the launch
line is in the aurora-agent docs/HTTP_API.md):
GET /v1/operations/snapshot?after=0&limit=15— mission summary, persistence checkpoints, consistency model, recent events, guarantees, non_claims, operator_actions.GET /v1/operations/gates?after=0&limit=40— per-group gate states.GET /v1/operations/domains?after=0&limit=40— observed activity per group.GET /v1/recovery— what restarts restore, and what they do not.
Reporting rules (non-negotiable)
readiness_claimed: falsemeans readiness is NOT claimed — never render a group as "ready" or "healthy" while it is false. Gate states likeinsufficient_evidenceandmissingare first-class findings; missing evidence is a state, not an absence to gloss over.- Quote
guarantees,non_claims,limitations,does_not_restore, andoperator_actionsarrays verbatim — they are the system's own honest boundary and must survive your summary. - Distinguish transport success from semantic success: a completed tool event proves a completed local call, not correctness. Refused tool events are counted separately — report them.
- Recovery: report
automatic_resume: falseand absent checkpoints exactly; the system deliberately never presents an absent checkpoint as recovered state. - Event pages carry
gapanddropped_events— ifgapis true, say that continuity cannot be claimed for the window you looked at.
Output shape
A short posture summary (counts: groups, insufficient-evidence groups, refused events, checkpoint presence), then per-area findings with the verbatim honesty fields, then the operator actions the system itself recommends. End with what you did NOT inspect (bounded pages, retention gaps) so the report's own coverage is honest.
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.
- 5d ago First seen · 52 lines · 77 tokens per session scan A 92fd874cb26d
ops-auditor is an agent published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 77 tokens to every session and 617 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
feedback-triage
Turns one narrated screen recording (processed by the talkthrough MCP server) into precise, evidence-backed findings plus a numbered confirm digest. Never files issues itself — it produces the findings JSON; filing happens only after the recording author approves.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.