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 agentmods add commands/modeled-information-format/mnemonic/validategit clone --depth 1 https://github.com/modeled-information-format/mnemonicWhat 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 | $0.00011 | $0.00575 |
| Opus 5 | $0.00005 | $0.00287 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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.
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
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.
- 2d ago First seen · 93 lines · 11 tokens per session scan A bf8e5668fa42
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.
Other commands, from other repositories
issue-review
Run Codex native + adversarial review against the active issue, scoped to allowedfiles, capped per kind.
wiring-check
End-of-task wiring gate — verify every change is connected end-to-end across kipi plugins, hooks, MCP tools, agents, bus files, canonical, and rules. Nothing dangling.
issue-closeout
Triage Codex findings via per-finding dispositions, record findingstriaged, close the active issue.
prd-personas
Run the Skeptic persona session against the active draft PRD.
linear-drain
Create the queued Linear projects and issues that shell scripts captured offline.
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.