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 skills add AURORA-NEURO/aurora-agent --skill aurora-setupgit 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/skills/aurora-neuro/aurora-agent/aurora-setup)<a href="https://agentmods.dev/skills/aurora-neuro/aurora-agent/aurora-setup"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/aurora-setup.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.00079 | $0.00660 |
| Opus 5 | $0.00039 | $0.00330 |
| Sonnet 5 | $0.00016 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
aurora-setup 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AURORA backend setup
The aurora-agent plugin launches bioprism-mcp, the MCP server of the
AURORA Agent workspace (264 tools; JSON-RPC 2.0 over newline-delimited stdio;
stdout is JSON-RPC only, diagnostics go to stderr).
Where the backend lives
The plugin's launcher (scripts/aurora-mcp.mjs) resolves the checkout in this
order and refuses with a precise stderr message if nothing matches:
AURORA_AGENT_ROOTenvironment variable~/aurora-agent~/bioprism
A directory qualifies when it contains Cargo.toml. Set AURORA_AGENT_ROOT
when the checkout lives anywhere else.
Build
git clone https://github.com/AURORA-NEURO/aurora-agent
cd aurora-agent
cargo build --release --offline -p bioprism-mcp
The workspace builds offline against pinned versions (.cargo/config.toml
sets net.offline = true); you cannot add external crates. A release build of
the full three-binary set is -p bioprism-cli -p bioprism-mcp -p bioprism-api
and takes a long time (codegen-units = 1, thin LTO) — the MCP server alone is
faster.
Windows gotcha: os error 4551
If a freshly linked binary reports os error 4551 ("never executed"), Windows
Application Control blocked it — the program NEVER RAN, even though cargo
reports a failure. Touch a source file to force a relink and rebuild. In test
suites this silently truncates --workspace totals; a suite that never ran
looks like a suite that failed.
What --root means
The launcher passes --root <checkout>. Root is a confinement boundary:
every path a tool receives resolves inside it — absolute paths, .. traversal,
and symlink escapes are refused. The reference fixtures
(fixtures/fiber-v0.1/radiogenomic_world.json,
fixtures/fiber-v0.1/leakage_query.json) live inside root, so tool calls can
name them by that relative path.
Known caveat: the conformance_run tool bakes a build-machine fixtures path at
compile time; it only works when the checkout has not moved since it was built.
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.
- 7d ago First seen · 64 lines · 79 tokens per session scan A 7ea32c05b3f8
aurora-setup is a skill published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 660 once invoked, about $0.0004 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 skills, from other repositories
halopsa
Every HaloPSA, HaloITSM and HaloCRM feature, plus a local SQLite store and cross-entity views the API can't return. Trigger phrases: triage my Halo queue, check SLA breaches in HaloPSA, who is overloaded in Halo, client card for Acme in Halo, Halo contract burn-down, what changed in Halo since this morning, find time…
veeam
Use when the user asks to check Veeam backup health across customers, find failing or stale backup jobs, surface workloads past their RPO, triage VSPC alarms, or report per-tenant license usage from a Veeam Service Provider Console. Syncs every tenant into a local SQLite mirror so it answers multi-tenant backup…
cipp
First single-binary CLI for CIPP - offline SQLite store, fleet posture analytics, and cross-tenant fan-out no other CIPP tool has. Trigger phrases: check MFA across all my tenants, find unused M365 licenses, offboard users from a CSV in CIPP, which tenants drifted off baseline, list CIPP tenants, use cipp, run…
immybot
Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions the web UI cannot. Trigger phrases: what failed in last night's maintenance window, which tenants are still on an old version of chrome, why didn't this computer get the deployment, what changed in the fleet since…
appdirect
Every documented AppDirect marketplace operation in one binary, plus offline sync and billing-reconciliation joins. Trigger phrases: reconcile appdirect billing, which appdirect payments failed this week, what changed in appdirect subscriptions, show my appdirect pipeline, appdirect company 360, use appdirect, run…
connectwise-manage
Every ConnectWise PSA workflow from the terminal - with a typed conditions query builder, offline SQLite sync, and cross-entity views (unbilled work, account 360, board triage) the PSA web UI can't give you. Trigger phrases: list connectwise tickets, triage the help desk board, find unbilled time in connectwise…