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/Project-VIC-International/Agentic-AI-Development-CourseWrote 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/rules/project-vic-international/agentic-ai-development-course/ontology-alignment)<a href="https://agentmods.dev/rules/project-vic-international/agentic-ai-development-course/ontology-alignment"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/ontology-alignment/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/rules/project-vic-international/agentic-ai-development-course/ontology-alignment"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/ontology-alignment.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.03190 | $0.03190 |
| Opus 5 | $0.01595 | $0.01595 |
| Sonnet 5 | $0.00638 | $0.00638 |
| Haiku 4.5 | $0.00319 | $0.00319 |
Grade A, and why
ontology-alignment 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 8d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CASE / UCO / CAC Ontology Alignment
This project is built on a stack of interlocking open ontologies. Every data structure, export, and internal representation MUST be grounded in these ontologies to enable true interoperability with the digital investigation and Project VIC communities, and to ensure court-defensible, scientifically rigorous output.
The Ontology Stack
| Layer | Ontology | What It Covers | Where to Find It |
|---|---|---|---|
| Foundation | UCO — Unified Cyber Ontology | Core cyber-domain concepts (files, accounts, devices, identities, locations, time) | https://unifiedcyberontology.org/ · https://github.com/ucoProject |
| Investigation | CASE — Cyber-investigation Analysis Standard Expression | Investigations, investigative actions, evidence, provenance, chain of custody | https://caseontology.org/ · https://github.com/casework |
| Domain | CAC Ontology — Crimes Against Children Ontology | Grooming, exploitation indicators, victim/offender modeling, Project VIC categories, analyst wellbeing | https://site.cacontology.projectvic.org/ · https://github.com/Project-VIC-International/CAC-Ontology |
| Forensic Science (optional but encouraged) | SOLVE-IT | Forensic techniques, weaknesses, mitigations, tool profiles, ASTM E3016-18 error categories | https://ontology.solveit-df.org/ · https://github.com/SOLVE-IT-DF/solve-it-ontology |
Use UCO/CASE/CAC at minimum. Add SOLVE-IT when your tool performs a documented forensic analysis whose error modes need to be defensible in court (carving, hashing, perceptual hashing, AI classification, OCR, timeline reconstruction, etc.). For CAC tools that may end up cited in trial exhibits, SOLVE-IT alignment is strongly recommended.
Why Each Ontology Matters in Plain Language
- UCO is the dictionary. Every cyber thing — a file, an account, a phone number, an IP address — has a UCO class with a stable IRI. Without UCO, two agencies cannot agree on what the word "file" means in machine-readable form.
- CASE is the grammar of an investigation. It connects observations to the actions that produced them, ties evidence to chain-of-custody actors, and gives every assertion a provenance trail.
- CAC Ontology speaks the specific vocabulary of Crimes Against Children work. It defines categories like grooming stages, Project VIC CSAM categorization, victim age estimation, and analyst wellbeing exposures. It is the layer that lets a CAC investigator's tool output be understood by another CAC investigator's tool.
- SOLVE-IT is the layer that makes your output defensible. It catalogues the known weaknesses of every forensic technique, the mitigations that address them, and the ASTM E3016-18 error categories that defense counsel will ask about on cross-examination. A SOLVE-IT-aligned tool tells the court not just "we found this," but "we found this using technique T, which has weakness W, which we mitigated with M, and the residual error category is E."
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.
- 8d ago First seen · 166 lines · 3,190 tokens per session scan A 27784bf09894
ontology-alignment is a cursor rule published in the GitHub repository Project-VIC-International/Agentic-AI-Development-Course (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 3,190 tokens to every session, about $0.0159 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.