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 agentmods add skills/humanerd-drew/opencode-drewgent/ontology-querynpx skills add humanerd-drew/opencode-drewgent --skill ontology-querygit clone --depth 1 https://github.com/humanerd-drew/opencode-drewgentWrote 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/humanerd-drew/opencode-drewgent/ontology-query)<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/ontology-query"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/ontology-query.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 | $0.00000 | $0.00729 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
ontology-query 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
title: ontology-query — OpenCrab Graph Query Tool type: document space: concept tags: [concept] created: 2026-05-21 updated: 2026-05-20 links:
- "[[@memory/growth/open-crab-ontology-{{AGENT_NAME_LOWER}}-implementation]]"
- "[[@memory/knowledge/NEURONFS_RULES]]"
- "[[@memory/knowledge/OPENCRAB_ONTOLOGY]]"
- "[[@memory/scripts/ontology_frontmatter_sync.py]]"
- "[[@identity/brain/rules]]"---
ontology-query — OpenCrab Graph Query Tool
Query the P0-brainstem ontology graph exported as JSONL.
Script Location
~/.{{AGENT_NAME_LOWER}}/P4-cortex/scripts/ontology_query.py
Commands
# 1. List all nodes
python3 P4-cortex/scripts/ontology_query.py list
# 2. Show space distribution
python3 P4-cortex/scripts/ontology_query.py spaces
# 3. Get a specific rule
python3 P4-cortex/scripts/ontology_query.py rule <rule_id>
# 例: python3 P4-cortex/scripts/ontology_query.py rule 禁karpathy_coding_principles
# 4. Show links in/out for a rule
python3 P4-cortex/scripts/ontology_query.py links <rule_id>
# 5. Show full graph connections (1st + 2nd degree)
python3 P4-cortex/scripts/ontology_query.py graph <rule_id>
# 6. Search by title or rule_source
python3 P4-cortex/scripts/ontology_query.py search <query>
# 例: python3 P4-cortex/scripts/ontology_query.py search karpathy
# 7. Find orphan nodes (no links)
python3 P4-cortex/scripts/ontology_query.py orphans
# 8. Filter by space
python3 P4-cortex/scripts/ontology_query.py space <space>
# 例: python3 P4-cortex/scripts/ontology_query.py space policy
Output Examples
spaces
Space Distribution:
policy 13
Total: 13 nodes
links <rule_id>
Links FROM 禁karpathy_coding_principles:
→ P0-brainstem/brain/{{AGENT_NAME}}-brain/P0-brainstem/禁/禁brain_obsidian_graph
→ P0-brainstem/brain/rules
→ P5-ego/SELF_MODEL
Links TO 禁karpathy_coding_principles:
(none — orphan candidate)
orphans
No orphan nodes found. All nodes have at least one connection.
Ontology File
~/.{{AGENT_NAME_LOWER}}/P0-brainstem/p0-brain-ontology.jsonl
13 nodes exported as JSONL. Updated manually when new .neuron files are created.
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.
- 5d ago First seen · 92 lines · 0 tokens per session scan A 69e890550d06
ontology-query is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 729 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…