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 Abilityai/cornelius --skill ref-bridgegit clone --depth 1 https://github.com/Abilityai/corneliusWrote 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/abilityai/cornelius/ref-bridge)<a href="https://agentmods.dev/skills/abilityai/cornelius/ref-bridge"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/ref-bridge.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.00094 | $0.02137 |
| Opus 5 | $0.00047 | $0.01069 |
| Sonnet 5 | $0.00019 | $0.00427 |
| Haiku 4.5 | $0.00009 | $0.00214 |
Grade A, and why
ref-bridge 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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ref Bridge
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.ref-bridge v1.0 — recent: initial version. Then proceed.
Why reference data lives in the brain and not in a spreadsheet. A CRM stores clients; a second brain can tell you which of your insights a client is a live instance of. ref-bridge mounts a reference sub-scope alongside core and finds the bridges from an entity to the user's cognitive notes ("Acme Corp, the lighthouse deal ↔ your note on land-and-expand / reference-customer leverage").
It is read-only sense. It surfaces candidates; it never writes, and — critically — it never promotes a record into an endorsed insight. A record informing a thought is fine; a record becoming the user's originated/endorsed thought is the one line the reference kind exists to hold, and it stays the human encountered → endorsed act.
Read first: resources/layered-brains/COMPANY-BRAIN-SCHEMA.md → "The playbook suite" (ref-bridge row) + "Automation boundary"; resources/layered-brains/REFERENCE-SCOPE-SCHEMA.md.
Composes
/find-connections— the connection-discovery engine; this skill runs it with the reference scope mounted and frames the output as entity→cognitive-note bridges. (Do not re-implement connection logic.)
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Company family | Brain/Company/*/*.md |
✓ | The entity anchor(s) | |
| Core KB + wrappers | Brain/{02-Permanent,03-MOCs,AI Extracted Notes,01-Sources}/, resources/local-brain-search/run_connections.sh · run_search.sh |
✓ | Bridged-to cognitive notes |
Process
Step 1 — Pick the anchor + read its themes
Resolve the entity note (or take a whole sub-scope) and read it to extract its distinctive themes — the economic/strategic concepts it embodies, not its proper nouns (e.g. Acme Corp's engagement = "one lighthouse deal deposits a reusable blueprint + license ARR + a reference case" → themes: optionality / one-bet-many-payoffs, reusable-asset leverage, reference-proof credibility). These themes are the query surface — the bridge is to the insight a fact instantiates, so search by concept.
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.
- 3d ago First seen · 81 lines · 94 tokens per session scan A 0bc7998b0f07
ref-bridge is a skill published in the GitHub repository Abilityai/cornelius (106 stars, last pushed 14d ago), licensed MIT. It adds 94 tokens to every session and 2,137 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.