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 mxyhi/ok-skills --skill ontoly-software-graphgit clone --depth 1 https://github.com/mxyhi/ok-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/mxyhi/ok-skills/ontoly-software-graph)<a href="https://agentmods.dev/skills/mxyhi/ok-skills/ontoly-software-graph"><img src="https://agentmods.dev/badge/skills/mxyhi/ok-skills/ontoly-software-graph/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/mxyhi/ok-skills/ontoly-software-graph"><img src="https://agentmods.dev/badge/skills/mxyhi/ok-skills/ontoly-software-graph.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.00040 | $0.00561 |
| Opus 5 | $0.00020 | $0.00280 |
| Sonnet 5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
ontoly-software-graph 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ontoly Software Graph
Use this skill when a coding agent needs graph-backed understanding of a TypeScript repository. Ontoly is the source of truth; the skill only teaches the workflow.
When to Use
- Explain repository architecture or package/module topology
- Trace a route, controller, service, function, or dependency path
- Find services, controllers, providers, modules, routes, configuration, or environment variables
- Estimate impact before refactoring or deleting code
- Audit unresolved imports, circular dependencies, dead code, semantic coverage, or graph quality
- Produce onboarding, documentation, or architecture-review notes with deterministic evidence
Workflow
-
Check whether an Ontoly graph already exists:
.ontoly/,SoftwareGraph.json,diagnostics.json, validation reports, graph hash, or MCP setup. -
If the graph is missing and local analysis is allowed, run:
ontoly build . -
Inspect graph health before answering: diagnostics, graph hash, semantic coverage, trust or quality score, framework detection, and build timestamp.
-
Prefer Ontoly CLI or MCP capabilities over repository search for graph-answerable questions.
-
Search source files only when Ontoly cannot answer, the graph is stale or incomplete, or the user explicitly asks for file-level verification.
-
Always cite graph evidence: node IDs, edge types, file paths, source locations, diagnostics, framework analyzer output, and confidence.
Capability Map
- Architecture review:
ExplainArchitecture - Dependency analysis:
FindDependencies - Impact analysis:
ImpactAnalysis - Request tracing:
TraceExecution - Configuration analysis:
FindConfigurationUsage - Framework analysis:
FrameworkReport - Dead-code review:
FindDeadCode
Response Pattern
Return the direct answer first, then evidence:
AuthController handles authentication.
Evidence:
- node: class:src/auth/auth.controller.ts:AuthController
- route edges: HANDLES POST /login and POST /logout
- dependency edges: USES AuthService and JwtService
Confidence: high, because the graph has controller, route, and dependency edges with source locations.
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.
- 10d ago First seen · 65 lines · 40 tokens per session scan A 67bca3901146
ontoly-software-graph is a skill published in the GitHub repository mxyhi/ok-skills (484 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 561 once invoked, about $0.0002 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
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
debugging-and-error-recovery
Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
pm-fix
Skill "pm-fix" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
pm-checkup
On-demand five-dimension project checkup (security, function, completeness, quality, docs) with P0/P1/P2. No cron.