Borrowing it
Nothing to install: this file belongs to wlsdks/ontology-atlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wlsdks/ontology-atlas/main/.agents/skills/ontology-bootstrap/SKILL.mdgit clone --depth 1 https://github.com/wlsdks/ontology-atlasWrote 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/wlsdks/ontology-atlas/ontology-bootstrap)<a href="https://agentmods.dev/skills/wlsdks/ontology-atlas/ontology-bootstrap"><img src="https://agentmods.dev/badge/skills/wlsdks/ontology-atlas/ontology-bootstrap/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/wlsdks/ontology-atlas/ontology-bootstrap"><img src="https://agentmods.dev/badge/skills/wlsdks/ontology-atlas/ontology-bootstrap.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.00129 | $0.07981 |
| Opus 5 | $0.00064 | $0.03991 |
| Sonnet 5 | $0.00026 | $0.01596 |
| Haiku 4.5 | $0.00013 | $0.00798 |
Grade A, and why
ontology-bootstrap 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 6d 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 — 710 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap a trustworthy ontology
Create a shared meaning model, not a labeled file tree. Treat repository structure as implementation evidence. Never promote a folder, package, README heading, or model-generated phrase into a business concept without a definition and source-backed justification.
Use only ontology-atlas MCP tools for the core workflow. Do not depend on CodeGraph, another skill, shell search, or an AST index. Those may exist, but a plain agent connected only to Atlas must still succeed at the meaning model. The optional, bounded task-navigation enrichment below is the sole exception: after meaning selects a stable element, a source-aware builder may use an available local source reader to verify exact coordinates that Atlas then checks again. Navigation may remain unknown without blocking the core model.
Meaning contract
The normative five-kind discriminator, relation support matrix, direct
is_a test, and inference/standards boundary live only in the
Atlas meta-model specification.
This skill owns the bootstrap sequence and evidence/approval states; it does
not redefine the model. If the linked file is unavailable, use the compact
meta-model boundary supplied by the connected Atlas MCP instructions.
Keep these epistemic states separate:
observed: directly present in a returned source excerpt, path, package, or import.proposed: an interpretation supported by observed evidence but not yet accepted by the user.shared: a user-approved concept persisted in the vault.
Before extracting concepts, read guides/meaning-extraction.md. Apply its definition, boundary, evidence, naming, relation, and self-audit rules.
Workflow
1. Confirm cold-start scope
Call:
connection_info({})
list_kinds({})
Compare both roots returned by connection_info with the intended absolute
vault and repository before calling list_kinds or reading project evidence.
On any mismatch, stop that process immediately; do not send a harmless-looking
read to learn whether the wrong server might still work. A source checkout that
already exposes its own dogfood MCP is especially easy to mistake for the new
vault.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · +13 lines 4188bcf781be
- 8d ago Changed · +24 lines c4a19a4c9ea0
- 13d ago First seen · 673 lines · 129 tokens per session scan A 790bf18b1d8c
ontology-bootstrap is a skill published in the GitHub repository wlsdks/ontology-atlas (104 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 7,981 once invoked, about $0.0006 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-30.
Other skills, from other repositories
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
open-ontologies
AI-native ontology engineering using 50+ MCP tools backed by an in-memory Oxigraph triple store. Build, validate, query, and govern RDF/OWL ontologies with a generate-validate-iterate loop. Use when building ontologies, knowledge graphs, RDF data, SPARQL queries, BORO/4D modeling, SHACL validation, clinical…
mykg
Run mykg knowledge-graph commands inside Claude Code from one slash command /mykg. The user describes intent in natural language (extract, append, sync, resume, approve, walkthrough, parse-docs, fetch-web, query); the skill parses intent, builds the right mykg CLI command from the live --help output, confirms, runs…
accurate-code
Use when implementing or modifying code with Kontext Brain so each behavior-bearing logic unit is grounded in current provenance-backed decisions, domain terms, invariants, and Evidence.
container-manager-kg-ingestion
Snapshot a host's Docker/Podman/Swarm inventory into the epistemic-graph knowledge graph as typed OWL nodes via the container-manager-mcp MCP server — containers, images, volumes, networks, swarm services and nodes, with their :usesImage / :runsOn / :builtFrom links. Use when the agent must record live container state…
action-contract-execution-feedback-loop
A specification method for making a business action into a tool an AI agent can call safely. It defines the action’s inputs, outputs, permissions, preconditions, expected effects, error handling, and audit information.