validate

A command that checks an ontology YAML file against its required schema. An ontology is a structured description of entity types, traits, relationships, and discovery rules.

In plain words
What is it for?
It is for validating ontology IDs, versions, base types, traits, relationships, and regular-expression discovery patterns, with optional JSON output.
Why use it?
It catches missing fields, invalid formats, unsupported types, and broken references before the file is used.

Command

Install

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.

agentmods
npx agentmods add commands/modeled-information-format/mnemonic/validate
Clone the repo
git clone --depth 1 https://github.com/modeled-information-format/mnemonic
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 575 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00575
Opus 5 $0.00005 $0.00287
Sonnet 5 $0.00002 $0.00115
Haiku 4.5 $0.00001 $0.00057

Measured 2d ago against content hash bf8e5668fa42, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

validate 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 2d 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.

commands/validate.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory

Search first: /mnemonic:search {relevant_keywords} Capture after: /mnemonic:capture {namespace} "{title}"

Run /mnemonic:list --namespaces to see available namespaces from loaded ontologies.

Validate Ontology

Validates an ontology definition file for correctness.

Usage

/mnemonic:validate <file> [--json]

Arguments

  • <file> - Path to ontology YAML file (required). Defaults to $MNEMONIC_ROOT/ontology.yaml
  • --json - Output as JSON

Checks Performed

  • Required fields present (id, version)
  • ID format (lowercase, hyphens)
  • Version follows semver
  • Valid base types (semantic, episodic, procedural)
  • Traits defined before use
  • Relationships reference valid entity types
  • Discovery patterns are valid regex

Procedure

# Resolve MNEMONIC_ROOT from config
if [ -f "$HOME/.config/mnemonic/config.json" ]; then
    RAW_PATH=$(python3 -c "import json; print(json.load(open('$HOME/.config/mnemonic/config.json')).get('memory_store_path', '~/.claude/mnemonic'))")
    MNEMONIC_ROOT="${RAW_PATH/#\~/$HOME}"
else
    MNEMONIC_ROOT="$HOME/.claude/mnemonic"
fi
ONTOLOGY_FILE="${1:-$MNEMONIC_ROOT/ontology.yaml}"
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(dirname $(dirname $0))}"

python3 "$PLUGIN_DIR/skills/ontology/lib/ontology_validator.py" "$ONTOLOGY_FILE" ${ARGS}

If Python validation unavailable, perform basic YAML checks:

# Check file exists
if [ ! -f "$ONTOLOGY_FILE" ]; then
    echo "Error: File not found: $ONTOLOGY_FILE"
    exit 1
fi

# Check required fields
if ! grep -q "^ontology:" "$ONTOLOGY_FILE"; then
    echo "Error: Missing 'ontology:' section"
    exit 1
fi

if ! grep -q "id:" "$ONTOLOGY_FILE"; then
    echo "Error: Missing 'id' field"
    exit 1
fi

echo "Basic validation passed for: $ONTOLOGY_FILE"

Example Output

Validating: my-ontology.yaml
Status: VALID

Warnings (1):
  - [WARNING] traits.cited: Trait has no fields or requires defined

Read the full file on GitHub · 93 lines

Changes

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.

  1. 2d ago First seen · 93 lines · 11 tokens per session scan A bf8e5668fa42

Subscribe to this mod's changes

validate is a command published in the GitHub repository modeled-information-format/mnemonic (22 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 575 once invoked, about $0.0001 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.