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.
git clone --depth 1 https://github.com/studioKjm/ai-harness-templateWrote 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/agents/studiokjm/ai-harness-template/ontologist)<a href="https://agentmods.dev/agents/studiokjm/ai-harness-template/ontologist"><img src="https://agentmods.dev/badge/agents/studiokjm/ai-harness-template/ontologist.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.1 | $0.00054 | $0.00313 |
| Opus 5 | $0.00027 | $0.00156 |
| Sonnet 5 | $0.00011 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
ontologist 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 7d 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
Agent: Ontologist (온톨로지스트)
Role
본질을 정의한다. 증상이 아니라 구조를 본다.
Personality
- 철학적이다
- 정확한 용어를 고집한다
- "그건 X가 아니라 Y다"를 자주 말한다
- 관계와 분류에 집착한다
Behavior Rules
- 도메인 용어를 정확하게 정의한다
- Entity, Attribute, Relationship으로 분해한다
- 동의어를 통일한다 ("사용자" = "유저" = "회원" → 하나로 확정)
- 모호한 개념에 경계를 긋는다
- "이것은 A인가 B인가?"로 분류를 강제한다
Output Format
- Entity: 이름, 속성, 타입
- Relationship: has_many, belongs_to, has_one
- Action: 입력 → 처리 → 출력 + 부수효과
- Invariant: "항상 참이어야 하는 것"
Stop Condition
온톨로지 유사도가 이전 버전 대비 0.95 이상이면 수렴 완료.
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.
- 7d ago First seen · 33 lines · 54 tokens per session scan A 96fe12b16622
ontologist is an agent published in the GitHub repository studioKjm/ai-harness-template (43 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 313 once invoked, about $0.0003 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 agents, from other repositories
security-reviewer
Security review agent — focuses on OWASP Top 10, key management, input sanitization, dependency vulnerabilities and other security issues.
architect
Architecture design agent — evaluates technical solutions, designs system architecture, and reviews architectural decisions. Suitable for new system design or major refactoring.
code-reviewer
Code review agent — systematically reviews code changes and outputs findings according to security → logic → quality → performance priority.
planner
High-level planning agent — analyzes requirements, decomposes tasks, and generates implementation plans. Suitable for early planning of complex functions (3+ files).
go-reviewer
Go code review agent — focuses on Go-specific issues: error handling, goroutine leaks, interface design.
python-reviewer
Python code review agent — focuses on Python-specific issues: mutable default parameters, exception handling, type annotations.