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/eliransu/digital-brain/savenpx skills add eliransu/digital-brain --skill savegit clone --depth 1 https://github.com/eliransu/digital-brainWrote 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/eliransu/digital-brain/save)<a href="https://agentmods.dev/skills/eliransu/digital-brain/save"><img src="https://agentmods.dev/badge/skills/eliransu/digital-brain/save.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.00112 | $0.01095 |
| Opus 5 | $0.00056 | $0.00548 |
| Sonnet 5 | $0.00022 | $0.00219 |
| Haiku 4.5 | $0.00011 | $0.00110 |
Grade A, and why
save 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 4d 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
88% identical to save — 31 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
save: File Conversations Into the Wiki
Good answers and insights shouldn't disappear into chat history. This skill takes what was just discussed and files it as a permanent wiki page.
The wiki compounds. Save often.
Note Type Decision
Determine the best type from the conversation content:
| Type | Folder | Use when |
|---|---|---|
| synthesis | wiki/synthesis/ | Multi-step analysis, comparison, or answer to a specific question |
| concept | wiki/concepts/ | Explaining or defining an idea, pattern, or framework |
| source | wiki/sources/ | Summary of external material discussed in the session |
| decision | wiki/meta/ | Architectural, project, or strategic decision that was made |
| session | wiki/meta/ | Full session summary: captures everything discussed |
If the user specifies a type, use that. If not, pick the best fit based on the content. When in doubt, use synthesis.
Save Workflow
- Scan the current conversation. Identify the most valuable content to preserve.
- Ask (if not already named): "What should I call this note?" Keep the name short and descriptive.
- Determine note type using the table above.
- Extract all relevant content from the conversation. Rewrite it in declarative present tense (not "the user asked" but the actual content itself).
- Create the note in the correct folder with full frontmatter.
- Flywheel: file new people BEFORE wikilinking. Scan the note's body for distinct person names. Read
wiki/entities/people/_index.md. For each name not yet filed (no page inwiki/entities/people/<Full Name>.mdand no alias match), invoke thepplskill's add flow to create a page. Use the conversation context for role/relationship; if uncertain, file withrole: "—"+ a> [!todo] Confirm rolecallout. Defaultcompany: Your Organizationunless the source says otherwise. Track newly-filed names and show them in the final confirmation. Never emit a[[Name]]wikilink to a non-existent page — phantom links rot the graph. - Collect links: identify any wiki pages mentioned in the conversation. Add them to
relatedin frontmatter. - Update
wiki/index.md. Add the new entry at the top of the relevant section. - Append to
wiki/log.md. New entry at the TOP:## [YYYY-MM-DD] save | Note Title - Type: [note type] - Location: wiki/[folder]/Note Title.md - From: conversation on [brief topic description] - Update
wiki/hot.mdto reflect the new addition. - Confirm: "Saved as [[Note Title]] in wiki/[folder]/."
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.
- 4d ago First seen · 122 lines · 112 tokens per session scan A c19184285608
save is a skill published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 3mo ago), licensed MIT. It adds 112 tokens to every session and 1,095 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to save, differing in 31 lines, and is treated as a copy.
Other skills, from other repositories
llm-wiki
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
mindbase
Maintain a persistent AI-tended research wiki. Activates when the user wants to ingest a source (PDF, URL, article, paste), capture a thought, build the wiki context, query what's already known, lint for orphans/contradictions, or maintain page conventions. Phrases include "add this to my wiki", "today I decided…"…
migrate
Scan the project and migrate existing documentation into OKF format. Use when the user wants to populate the knowledge base from existing docs, README, schemas, API specs, runbooks, or any structured project knowledge. Trigger on "migrate to okf", "populate the knowledge base", "scan my docs", "convert docs to okf"…
setup
Scaffold a complete knowledge system. Detects platform, conducts conversation, derives configuration, generates everything. Validates against 15 kernel primitives. Triggers on "/setup", "/setup --advanced", "set up my knowledge system", "create my vault".