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 tony/skills --skill ontologygit clone --depth 1 https://github.com/tony/skillsWrote 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/tony/skills/ontology)<a href="https://agentmods.dev/skills/tony/skills/ontology"><img src="https://agentmods.dev/badge/skills/tony/skills/ontology/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/tony/skills/ontology"><img src="https://agentmods.dev/badge/skills/tony/skills/ontology.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00031 | $0.01136 |
| Opus 5 | $0.00015 | $0.00568 |
| Sonnet 5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
ontology 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.
This is a copy
88% identical to scholar-ontology — 62 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scholar:ontology
Distil what a corpus calls things into a type hierarchy, a controlled vocabulary, and an evidence layer. The product is a study directory, not a document, and every claim in it either cites a pinned source or carries a command that reproduces its number.
Read ../../references/evidence-tiers.md before starting; it decides what
each claim must carry. ../../references/citation.md governs every pin.
../../references/stage-gates.md states each stage's exit condition.
User arguments: $ARGUMENTS
Core thesis
An agent that has read a corpus usually returns a summary. A summary cannot be checked, does not compose, and rots without saying so.
The test this pipeline is built against:
CAN A READER WHO WAS NOT PRESENT DISAGREE WITH A CLAIM,
FIND WHAT IT RESTS ON, AND RE-DERIVE IT?
A study that fails that test is a summary with more sections.
Context
Repository:
!git remote get-url origin 2>/dev/null || echo "(not a git repository)"
Current ref:
!git rev-parse --short HEAD 2>/dev/null || echo "(unknown)"
Existing studies:
!ls notes/ontology/ 2>/dev/null || echo "(none)"
Stages
Five stages, run in order. Each is separately invocable, so a study resumes where it stopped rather than restarting.
/scholar:gather— resolve and pin the corpus, inventory it, and record what was read and what was skipped, intosources.jsonl./scholar:extract— harvest the terms the corpus uses, with a citation and a locator each, intoterms.jsonl./scholar:distill— build the three layers: types, members with discriminators, and the controlled vocabulary./scholar:contest— judge the ontology adversarially, one candidate at a time, recording the kills./scholar:render— writebrief.mdand the evidence documents, and gate the brief.
For prose, run /scholar:annotate before extract to produce quotations with
stable locators.
--resume=<stage> starts at that stage against an existing study directory.
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 First seen · 117 lines · 31 tokens per session scan A aafccffd6eb0
ontology is a skill published in the GitHub repository tony/skills (2 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 1,136 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to scholar-ontology, differing in 62 lines, and is treated as a copy.
Other skills, from other repositories
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
postgres-hybrid-text-search
Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…