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/hax-studio/mnemonica/setupnpx skills add HAX-Studio/mnemonica --skill setupgit clone --depth 1 https://github.com/HAX-Studio/mnemonicaWrote 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/hax-studio/mnemonica/setup)<a href="https://agentmods.dev/skills/hax-studio/mnemonica/setup"><img src="https://agentmods.dev/badge/skills/hax-studio/mnemonica/setup.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.01856 |
| Opus 5 | $0.00032 | $0.00928 |
| Sonnet 5 | $0.00013 | $0.00371 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
setup 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mnemonica: setup
Install Mnemonica's documentation system into a project: the algorithm block in
.claude/CLAUDE.md, the knowledge/ folder, and — for a project that already has code —
an initial population of module files. Read
${CLAUDE_PLUGIN_ROOT}/references/knowledge-conventions.md before starting; it is the
authority for every convention referenced below.
If the user's invocation includes extra wording beyond the trigger phrase (for example, "set up mnemonica and also use graphify for navigation"), treat it as scoping or preference for this run — it can add a companion tool to consult, narrow attention to part of the project, or similar. It cannot skip a step below or turn a step that never asks permission into one that silently does something riskier than described here.
Step 1: Locate the project root
Use the root of the current git repository (or the current working directory if there is no git repository yet) as the project root. All paths below are relative to it.
Step 2: Check git availability
Run git -C <project-root> rev-parse --is-inside-work-tree (or equivalent). If it fails,
this project has no git repository yet. This doesn't block installation, but it does limit
what will work afterward:
audit-fullstill works — it falls back to a plain directory scan when there's no git.audit-lightcannot work at all — its entire mechanism is diffing between two commits. Without git there is no "since the last checkpoint" to compute.
Mention this to the user in the Step 8 report rather than silently proceeding as if nothing
were different, and suggest that even a local-only git init (no remote required) is enough
to unlock audit-light later — Mnemonica never requires a remote, only local history.
Step 3: Install the CLAUDE.md block, non-destructively
Read .claude/CLAUDE.md if it exists.
- If it contains
<!-- MNEMONICA:BEGIN -->...<!-- MNEMONICA:END -->markers, replace only the content between them with the current contents of${CLAUDE_PLUGIN_ROOT}/skills/setup/assets/claude-md-block.template.md. This is what makes re-running setup safe (it upgrades Mnemonica's own block without touching anything else). - If the file exists but has no markers, append the template block to the end of the file, after a blank line. Do not alter, reorder, or remove any existing content — that content belongs to the project and may encode rules Mnemonica knows nothing about (for example, a project-specific instruction to use some other code-navigation tool). Preserving it is not optional.
- If the file does not exist, create
.claude/and.claude/CLAUDE.mdcontaining only the template block.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 128 lines · 65 tokens per session scan A d587fa021f0c
setup is a skill published in the GitHub repository HAX-Studio/mnemonica (3 stars, last pushed 27d ago), licensed MIT. It adds 65 tokens to every session and 1,856 once invoked, about $0.0003 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 skills, from other repositories
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…
alive:my-context-graph
Render an interactive map of your world. Generates the world index from all walnut and bundle frontmatter, then produces a force-directed graph showing connections between walnuts, people, bundles, and tags. Opens in the browser.