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 Dianel555/DSkills --skill ontolygit clone --depth 1 https://github.com/Dianel555/DSkillsWrote 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/dianel555/dskills/ontoly)<a href="https://agentmods.dev/skills/dianel555/dskills/ontoly"><img src="https://agentmods.dev/badge/skills/dianel555/dskills/ontoly/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/dianel555/dskills/ontoly"><img src="https://agentmods.dev/badge/skills/dianel555/dskills/ontoly.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.00107 | $0.01190 |
| Opus 5 | $0.00053 | $0.00595 |
| Sonnet 5 | $0.00021 | $0.00238 |
| Haiku 4.5 | $0.00011 | $0.00119 |
Grade A, and why
ontoly 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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ontoly - Software Graph Analysis
Build and query deterministic Software Graphs for TypeScript repositories. Ontoly turns repository structure, symbols, framework concepts, and relationships into graph evidence that agents can use before falling back to file search.
Prerequisites
# Recommended: run through npx so the current published CLI is used
npx ontoly --help
If the project already has Ontoly installed, prefer the repository-local package manager command, such as pnpm ontoly, npm exec ontoly, or npx ontoly.
Quick Start
# From the repository root
npx ontoly build .
# Start MCP for agent integrations
npx ontoly mcp
# Inspect available commands
npx ontoly --help
Expected outputs may include .ontoly/SoftwareGraph.json, diagnostics, graph statistics, indexes, and metadata depending on the Ontoly version and repository configuration.
Tool Routing Policy
Prefer Ontoly Before File Search
| Task | Avoid | Use Ontoly |
|---|---|---|
| Architecture summary | Reading every README/source folder | Build graph, inspect graph statistics and architecture report |
| Impact analysis | Grep for identifier text | Query dependencies, callers, callees, and related nodes |
| Request flow | Manually follow controller/service files | Trace route/controller/service relationships |
| Configuration audit | Search .env names only |
Query configuration and environment-variable nodes |
| Dead code review | Guess from unused exports | Use graph diagnostics and unreachable/dead-code evidence |
When to Use Built-in Tools
- Ontoly is not installed and cannot be run in the environment
- The graph reports low coverage or missing framework support
- The question depends on source comments, prose documentation, generated artifacts, or runtime data not represented in the graph
- You need to verify a suspected graph gap
Workflow
Phase 1: Graph Readiness
- Locate the repository root.
- Check for an existing Ontoly graph, usually
.ontoly/SoftwareGraph.json. - If missing or stale, run:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 153 lines · 107 tokens per session scan A 3cf2e9d280c7
ontoly is a skill published in the GitHub repository Dianel555/DSkills (64 stars, last pushed 2d ago), licensed MIT. It adds 107 tokens to every session and 1,190 once invoked, about $0.0005 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-09-07.
Other skills, from other repositories
audit
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to "audit the project", "run a full audit", "project health check", "audit my code", "codebase audit", or "comprehensive review".
investigate
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken"…
consult-oracle
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says "ask the oracle", "consult oracle", "consult chatgpt", "I'm completely…
find-dead-code
Find dead code using parallel subagent analysis and optional CLI tools, treating code only referenced from tests as dead. Use when the user asks to "find dead code", "find unused code", "find unused exports", "find unreferenced functions", "clean up dead code", or "what code is unused". Analysis-only — does not modify…
polish-code
Stage, format, lint, test, review, smoke test, and re-run itself until stable. Use when the user asks to "polish code", "refine code", "iterate on code quality", "review loop", "clean up, test, and review loop", or "run the polish loop".
simplify-code
Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes"…