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 fiber-decision-contextgit 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/fiber-decision-context)<a href="https://agentmods.dev/skills/aurora-neuro/aurora-agent/fiber-decision-context"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/fiber-decision-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aurora-neuro/aurora-agent/fiber-decision-context"><img src="https://agentmods.dev/badge/skills/aurora-neuro/aurora-agent/fiber-decision-context.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.00937 |
| Opus 5 | $0.00036 | $0.00468 |
| Sonnet 5 | $0.00014 | $0.00187 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
fiber-decision-context 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 10d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FIBER decision contexts
FIBER compiles a world (typed facts + factors) and a query into a Decision Section plus a Context Certificate — a receipt stating exactly what was omitted and whether it could have changed the decision. Omissions are reported at every layer: layering hides volume, never the fact of an omission.
Where things are
- Checkout:
$AURORA_AGENT_ROOT→~/aurora-agent→~/bioprism. - CLI:
<root>/target/release/bioprism(.exe); run from the checkout root. - MCP tools (if the aurora-backend plugin is installed):
fiber_compile,fiber_refine,fiber_explain,fiber_verify,context_compare,world_validate— same Rust implementation as the CLI. - Reference fixtures: world
fixtures/fiber-v0.1/radiogenomic_world.json, queryfixtures/fiber-v0.1/leakage_query.json. On this pair the reference certificate digest isc0da17ffc80465258345c8a538171bfd868100cd883e9a20780a0dc5477e7ea4— a checkable expectation: three independent implementations (CPython, eager Rust, indexed store) agree on it byte for byte.
The workflow
- Validate the world (
world validate --world W; no--queryflag). - Explain the plan (
context explain) — always surface the passes that did NOT run with their verbatim reasons, and the omission manifest. - Compile (
context compile [--certificate-out C]). The oracle statusinvalidmeans the oracle found integrity violations in the data (e.g. identity/site/temporal/preprocessing leakage) — that is the finding, not a failure. Report witnesses verbatim. - Layer via MCP
fiber_compilewithlayer: L0..L4— L0 is the smallest honest layer (~200 estimated tokens on the reference pair vs ~1,900 full); each result carries a content-addressed refinement handle forfiber_refine.estimated_tokens.methodself-discloses that it is a heuristic, not a tokenizer — quote it when reporting token numbers. - Compare (
context compare) — judge strategies byverdict_preserving, never bystatusalone: a "valid" from a non-preserving strategy is a FALSE verdict. Reportcheapest_admissible_strategyverbatim even when it is a baseline (on the reference pair it isgraph-5-hop— an honest negative the project publishes deliberately). - Verify (
context verify --certificate C) — certificates verify without the engine that produced them.
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.
- 10d ago First seen · 70 lines · 71 tokens per session scan A df693911088c
fiber-decision-context is a skill published in the GitHub repository AURORA-NEURO/aurora-agent (1 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 937 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…
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…
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…