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 skills/mnemon-dev/mnemon/nanobotnpx skills add mnemon-dev/mnemon --skill nanobotgit clone --depth 1 https://github.com/mnemon-dev/mnemonWhat 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.00025 | $0.00764 |
| Opus 5 | $0.00013 | $0.00382 |
| Sonnet 5 | $0.00005 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
mnemon 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.
This is a copy
86% identical to mnemon — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mnemon
Workflow
- Remember:
mnemon remember "<fact>" --cat <cat> --imp <1-5> --entities "e1,e2" --source agent- Diff is built-in: duplicates skipped, conflicts auto-replaced.
- Output includes
action(added/updated/skipped),semantic_candidates,causal_candidates.
- Link (evaluate candidates from step 1 — use judgment, not mechanical rules):
- Review
causal_candidates: does a genuine cause-effect relationship exist?causal_signalis regex-based and prone to false positives — only link if the memories are truly causally related. - Review
semantic_candidates: are these memories meaningfully related? Highsimilarityalone is not sufficient — skip candidates that share keywords but discuss unrelated topics. - Syntax:
mnemon link <id> <candidate> --type <causal|semantic> --weight <0-1> [--meta '<json>']
- Review
- Recall:
mnemon recall "<query>" --limit 10
Commands
mnemon remember "<fact>" --cat <cat> --imp <1-5> --entities "e1,e2" --source agent
mnemon link <id1> <id2> --type <type> --weight <0-1> [--meta '<json>']
mnemon recall "<query>" --limit 10
mnemon search "<query>" --limit 10
mnemon import --dry-run <file>
mnemon import <file>
mnemon forget <id>
mnemon related <id> --edge causal
mnemon gc --threshold 0.4
mnemon gc --keep <id>
mnemon status
mnemon log
mnemon store list
mnemon store create <name>
mnemon store set <name>
mnemon store remove <name>
Usage with nanobot
Use the exec tool to run mnemon commands. Recall can run in the main conversation; delegate remember and link to a sub-agent via spawn to keep the main conversation clean.
exec(command="mnemon recall 'user preferences'")
exec(command="mnemon recall 'past decisions about auth'")
Import Historical Chats
When the user asks to import old chats, notes, or exported context, create a
memory_draft.json with schema_version: "1", insights entries containing
content, category, importance, tags, entities, and optional
created_at, plus optional edges using source_index, target_index,
edge_type, weight, and reason. Run mnemon import --dry-run <file>,
then run mnemon import <file> only after validation passes. After import,
verify with mnemon status and a focused mnemon search or mnemon recall.
Check the output errors field because imports can partially succeed.
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 · 67 lines · 25 tokens per session scan A 750197440e11
mnemon is a skill published in the GitHub repository mnemon-dev/mnemon (540 stars, last pushed 9d ago), licensed Apache-2.0. It adds 25 tokens to every session and 764 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to mnemon, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
kayba-stage-3-metrics
Define metrics from Kayba insights, implement them as Python measurement code, run against traces, and iterate until the metrics are clean and meaningful. Trigger when the user says "run stage 3", "define metrics", "build metrics", "compute baselines", or when invoked by the kayba-pipeline orchestrator. Requires…
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-4-rubric
Organize computed metrics into a tiered evaluation rubric with leading, lagging, and quality indicators. Trigger when the user says "run stage 4", "build rubric", "tier metrics", or when invoked by the kayba-pipeline orchestrator. Requires eval/baselinemetrics.json and eval/computebaselines.py to exist.
kayba-stage-6-hitl
Human-In-The-Loop gate that presents the action plan with full context, collects an informed approval/modification/rejection decision, and records the outcome. Trigger when the user says "run stage 6", "HITL review", "approve action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md…
kayba-pipeline
End-to-end agent evaluation and improvement pipeline. Takes a traces folder and optional HITL flag, then orchestrates sub-agents through 7 stages — each stage is its own skill invoked by a dedicated sub-agent. Trigger when the user says "run the pipeline", "kayba pipeline", "evaluate and fix", "full eval", "analyze…
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.