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 robotaitai/project-bedrock --skill ontology-inferencegit clone --depth 1 https://github.com/robotaitai/project-bedrockWrote 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/robotaitai/project-bedrock/ontology-inference)<a href="https://agentmods.dev/skills/robotaitai/project-bedrock/ontology-inference"><img src="https://agentmods.dev/badge/skills/robotaitai/project-bedrock/ontology-inference/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/robotaitai/project-bedrock/ontology-inference"><img src="https://agentmods.dev/badge/skills/robotaitai/project-bedrock/ontology-inference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01440 |
| Opus 5.5 | $0.00016 | $0.00576 |
| Sonnet 5.5 | $0.00008 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
ontology-inference 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 1mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ontology Inference
The bedrock system never imposes a fixed ontology. Branch names and structure must be inferred from the real project, not from templates or generic categories.
This skill covers the inference process: how to read a repo and determine its natural decomposition into memory branches.
For running the bootstrap script, see project-ontology-bootstrap.
For writing the resulting notes, see project-memory-writing.
Core principle
Use the project's own terminology. Branch names should sound like things this project's developers would naturally say in a standup. Not "architecture" or "conventions" -- those are generic catch-all names that hide structure.
Good branch names (from real projects):
perception,navigation,localization,safety(robotics)auth,billing,notifications,search(web app)training,inference,data-pipeline,evaluation(ML platform)cli,packaging,runtime,testing(developer tool)
Bad branch names to avoid:
architecture-- too generic, lumps unrelated concernsconventions-- usually belongs inside specific branchesoverview-- that's what MEMORY.md ismisc-- if it's misc, it doesn't belong in memory yet
Inference signals to read
Read these signals before deciding on branches:
Manifests and package files
package.json, pyproject.toml, Cargo.toml, go.mod, CMakeLists.txt, package.xml
What: tech stack, dependencies, declared modules/packages Branch signals: what frameworks, what services, what subsystems are named here?
Directory structure (top 2 levels)
What: how the developers decomposed the code Branch signals: folder names that recur across src/, packages/, services/, apps/ are often natural branches
Docs and READMEs
README.md, AGENTS.md, CLAUDE.md, docs/
What: the project's own description of itself Branch signals: section headers in README.md often map directly to branches
CI/CD configuration
.github/workflows/, .gitlab-ci.yml, Makefile
What: what jobs/stages exist; what is tested; what is deployed Branch signals: job names, build targets, test suites
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.
- 1mo ago First seen · 178 lines · 39 tokens per session scan A b22599a5d666
ontology-inference is a skill published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,440 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
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…