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 wlsdks/ontology-atlas --skill atlas-growgit 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/atlas-grow)<a href="https://agentmods.dev/skills/wlsdks/ontology-atlas/atlas-grow"><img src="https://agentmods.dev/badge/skills/wlsdks/ontology-atlas/atlas-grow/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/atlas-grow"><img src="https://agentmods.dev/badge/skills/wlsdks/ontology-atlas/atlas-grow.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.00079 | $0.00739 |
| Opus 5 | $0.00039 | $0.00369 |
| Sonnet 5 | $0.00016 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
atlas-grow 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 13d 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.
What it actually says
/atlas-grow — 다음에 채울 곳
규율 하나 — 제안 단계는 절대 쓰지 않는다
사람이 고른 것만 볼트에 들어간다. 지어낸 노드는 이 도구가 낼 수 있는 최악의 결과다 — 틀린 지도는 없는 지도보다 나쁘다. 없으면 사람이 직접 찾아보지만, 틀린 것이 있으면 그걸 믿고 결정한다.
- 지금 어디까지 왔나
query_ontology({ operation: 'agent_brief' })— 이 볼트의 시작점과 다음 행동query_ontology({ operation: 'growth_plan' })— 무엇이 비어 있나
- 후보를 근거로 거른다
받은 후보를 그대로 옮기지 않는다. 하나씩 셋을 통과해야 남는다.
- 실재하는가 — 이름만 그럴듯한 게 아니라 코드나 문서에 근거가 있나.
find_evidence({ title })로 확인한다. 코드 폴더가 묶여 있으면analyze_repo_structure·infer_imports가 근거를 준다. - 이미 있는가 —
query_concepts({ filter })로 비슷한 이름을 먼저 찾는다. 있으면 새로 만들지 말고 그것을patch_concept(expected_mtime함께)로 채운다. - 뜻이 있는가 — 자리 말고 다른 이유가 있어야 element 다. 파일 하나마다 노드 하나를 만들면 그건 지도가 아니라 파일 목록이다.
- 사람에게 보여 준다
한 번에 다섯 개까지. 줄마다 셋을 적는다 — ① 무엇을 ② 어디에 붙이고 ③ 왜 그렇게 보는지(근거). 「전부 만들까요?」라고 묻지 않는다. 번호를 붙여서 골라서 답할 수 있게 한다.
- 승인된 것만 쓴다 — 그리고 확인한다
- 노드:
add_concepts(많으면 50개씩 나눠서) - 노드가 전부 성공한 다음에 관계:
add_relations validate_vault({})→query_ontology({ operation: 'health' })
새 도메인은 저절로 프로젝트에 안 붙는다.
add_relation('<project>', 'domains/<새 도메인>', 'domains') 를 빠뜨리면
만들어 놓고 지도에 안 보인다. 4번의 health 가 그것을 잡는다.
이 스킬이 실패하는 방식
- 근거 없이 그럴듯한 이름을 만들어 낸다
- 이미 있는 것을 못 찾아 비슷한 노드를 하나 더 만든다
- 묻지 않고 쓴다
- 노드만 만들고 관계를 안 걸어서, 만든 것이 어디에도 안 보인다
- 쓰고 나서 확인을 안 해, 깨진 것을 사람이 나중에 발견한다
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.
- 13d ago First seen · 54 lines · 79 tokens per session scan A 239a6c39ae45
atlas-grow is a skill published in the GitHub repository wlsdks/ontology-atlas (104 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 739 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-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.