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/tasknpx skills add eliransu/digital-brain --skill taskgit 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.00115 | $0.02298 |
| Opus 5 | $0.00057 | $0.01149 |
| Sonnet 5 | $0.00023 | $0.00460 |
| Haiku 4.5 | $0.00012 | $0.00230 |
Grade A, and why
task 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
task: Create a Linear Issue + Mirror in the Vault
/task is the bridge between your local note system and Linear. Every /task invocation produces TWO artifacts:
- A Linear issue — the canonical work item, on the right team and (by default) the current cycle.
- A mirror note in
wiki/notes/withnote_kind: taskand the Linear ID embedded — so the next/sync//suppicks it up alongside reminders.
The mirror means a /task you filed five minutes ago shows up in /sup without needing a /sync first.
User identity: [email protected]. Vault root: ~/digital-brain/.
Invocation Forms
| Form | Action |
|---|---|
/task <title> |
new Linear issue, default team, current cycle, assigned to you |
/task <title> @<Person> |
assign to that person (resolves via Linear list_users + people index) |
/task <title> sprint:next |
put on next cycle instead of current |
/task <title> sprint:none |
no cycle |
/task <title> team:<TEAMKEY> |
override default team (e.g. team:ENG) |
/task <title> priority:<urgent|high|med|low> |
set Linear priority |
/task <title> due:<date> |
set due date on the issue |
Multiple modifiers compose: /task ship retro @Alice sprint:current priority:high due:2026-05-20.
If $ARGUMENTS is empty, show the forms and ask which one.
Config
Reads wiki/daily/_config.json. Required keys (created on first run if missing):
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 · 184 lines · 115 tokens per session scan A 4ffc72e57737
task is a skill published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 2,298 once invoked, about $0.0006 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…