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/writenpx skills add eliransu/digital-brain --skill writegit clone --depth 1 https://github.com/eliransu/digital-brainWhat 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.00102 | $0.01060 |
| Opus 5 | $0.00051 | $0.00530 |
| Sonnet 5 | $0.00020 | $0.00212 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
write 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 yesterday.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
write: Draft in your Voice
Whenever you is going to send or publish something, drafts go through VOICE.md. If the user just says "write X" or "draft X" without invoking this skill, still apply VOICE.md.
Style sources
~/digital-brain/VOICE.md- canonical do/don't list.~/digital-brain/wiki/meta/Voice.md- long reference with examples and registers.~/digital-brain/wiki/entities/people/_index.md- who knows whom, used to pick language (Hebrew/English) and tone.
Always read VOICE.md before drafting. If the draft is short, the rules are still binding.
Surfaces
| Invocation | Surface |
|---|---|
/write <free text> |
Infer surface from content. If ambiguous, ask. |
/write slack <message> |
Slack public channel. |
/write dm <name> <message> |
Slack DM. Hebrew if recipient is Israeli, English otherwise. |
/write email <recipient> <topic> |
Email. Infer internal vs external from recipient domain. |
/write post <topic> |
Long-form public (Reddit, LinkedIn, blog). |
/write reply <pasted> <intent> |
Reply matching the surface of the pasted message. |
/write rewrite <pasted draft> |
Rewrite an existing draft to comply with VOICE.md. |
If empty $ARGUMENTS, list the seven forms and ask.
Workflow
- Read
~/digital-brain/VOICE.md. Re-read every invocation. Rules evolve. - Identify the surface (see table). If ambiguous, ask one short question.
- If a name was given, look up the person in
wiki/entities/people/_index.mdto set tone. All output is English regardless of recipient. - Draft.
- Self-check against the don'ts in VOICE.md. The high-frequency ones:
- Em-dashes (replace with hyphens, commas, parentheses, or a new sentence).
- Emojis in drafted output (drop them).
- Parallel constructions, three-beat rhythms, "not X but Y" patterns (rephrase plain).
- Marketing verbs and hollow superlatives (delete or replace with a concrete verb).
- Fake intimacy openers, self-dialogue, heavy connectives, tagline closers (delete).
- "things"/"stuff"/"lots"/"many" where a concrete number or name exists (replace).
- Title in email signature (remove).
- "Dear team", "Hope this finds you well" (rewrite opener).
- Show only the final draft. Do not preface with "Here is your draft" or similar. Do not narrate the rules applied unless asked.
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.
- yesterday First seen · 79 lines · 102 tokens per session scan A 526f5a418077
write is a skill published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 3mo ago), licensed MIT. It adds 102 tokens to every session and 1,060 once invoked, about $0.0005 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
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…"…
project-maintainer
Maintain an llmwiki-style open-source project across the full framework pipeline. Use when the user says "maintain the project", "check my tasks", "update progress", "run phase gate", "do a monthly verify", "lint my wiki", "check stale entries", or invokes any form of ongoing project-keeping chore. Reads progress.md…
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…
llmwiki-query
Answer a question by querying the user's llmwiki. Use when the user asks about their own past work — "what did I decide about X", "what have I been working on", "how did I solve Y", "what's my preferred approach to Z", or any question that the wiki (built from their session history) might answer. Always read the wiki…