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-reviewgit 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-review)<a href="https://agentmods.dev/skills/wlsdks/ontology-atlas/atlas-review"><img src="https://agentmods.dev/badge/skills/wlsdks/ontology-atlas/atlas-review/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-review"><img src="https://agentmods.dev/badge/skills/wlsdks/ontology-atlas/atlas-review.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.00078 | $0.00711 |
| Opus 5 | $0.00039 | $0.00356 |
| Sonnet 5 | $0.00016 | $0.00142 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
atlas-review 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-review — 지금 이 볼트가 성한가
아무것도 쓰지 않는다. 이 스킬이 내놓는 것은 「무엇이 어긋났고 무엇을 부르면 고쳐지는가」 한 장이다. 고치는 것은 사람이 보고 정한 다음이다.
- 두 번 부른다
validate_vault({})— frontmatter 와 관계 참조가 성한가query_ontology({ operation: 'health' })— 그래프 무결성 검사 묶음
grep 이나 sed 로 frontmatter 를 직접 훑지 않는다. 같은 답을 더 느리게 얻고
관계 해석과 스키마 검증이 빠진다.
- 통과한 것은 말하지 않는다
성한 검사를 나열하는 보고는 읽는 사람 시간을 쓰고, 정작 손댈 것을 묻는다. 손댈 것이 있는 것만 적는다. 전부 성하면 한 줄로 끝낸다 — 「지금 손댈 곳 없음 · 노드 N · 관계 M」.
- 항목마다 셋을 적는다
| 무슨 일인가 | 사람 말 한 줄. 검사 이름을 그대로 옮기지 않는다 |
| 왜 문제인가 | 이대로 두면 화면에서 무엇이 안 보이거나 틀리게 보이는지 |
| 고치는 호출 | 복사해서 바로 쓸 수 있는 한 줄 |
자주 나오는 둘:
- 닿지 않는 노드(
components) — 프로젝트 뿌리에서 못 닿는 노드는 어느 프로젝트에도 안 속해서 지도에 안 나온다. 만들어 놓고 안 보이는 상태다. →add_relation('<project>', 'domains/<새 도메인>', 'domains') - 한쪽만 아는 관계(
relation_recommendations) — 역량이domain: X를 갖고 있는데X쪽에서 되받아 걸지 않았다. →add_relation('domains/X', 'capabilities/<역량>', 'capabilities')
- 프로젝트 의미가 노랗다면 — 여기서 멈춘다
meaning_assessment 는 사람 승인 없이 마무리하지 않는다. 프로젝트가 답할
다섯 질문은 「이 프로젝트가 무엇인가」에 대한 주장이라, 에이전트가 대신 확정할
수 없다. 무엇이 비었는지만 보여 주고 멈춘다.
이 스킬이 실패하는 방식
- 통과한 검사까지 나열해서 정작 손댈 것이 묻힌다
- 검사 이름을 그대로 옮겨 적고 뜻을 안 풀어 준다
- 문제만 적고 「고치는 호출」이 없다 — 그러면 읽는 사람이 다시 물어야 한다
- 물어보지도 않고 고쳐 버린다
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 · 78 tokens per session scan A eef90ea31649
atlas-review is a skill published in the GitHub repository wlsdks/ontology-atlas (104 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 711 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
memtrace-decision-memory
Use Cortex decision memory through the normal Memtrace MCP tools. Trigger for free-text questions about what was decided, chosen, rejected, banned, or established as a convention; for why a symbol exists or which contracts constrain it; for whether a known decision held, drifted, or was violated; and for the…
memtrace-index
Index a source-code repo into the Memtrace knowledge graph and poll the job to completion. Use when the user asks to index, parse, ingest, reindex, watch, or prepare a source-code repo for Memtrace analysis, when code exploration needs an index, or when searches return 0/partial results for source paths under an…
memtrace-session-continuity
Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed while away, recover prior context, or orient at session start without guessing timestamps. Do not…
memtrace-continuous-memory
Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory (meaning Memtrace index watching, not generic agent memory), or make just-saved…
repo-docs-intelligence-bootstrap
Use when a repository needs one lightweight repository memory profile that evolves with the codebase to reduce drift, prevent structural mistakes, and keep current repository truth plus durable working context explicit. Trigger for requests to refresh current-state or architecture docs from live code, classify or…
llm-wiki-bootstrap
Use this skill when the user wants to scaffold a new Obsidian-first LLM Wiki workspace, bootstrap Andrej Karpathy-style LLM Wiki structure, create raw/wiki/AGENTS.md layout in a fresh project, or standardize a markdown-first knowledge vault with scripts, templates, and meta pages. Trigger on requests to set up an LLM…