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 commands/superuser-pal/awesome-second-brain/processgit clone --depth 1 https://github.com/superuser-pal/awesome-second-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.00044 | $0.01158 |
| Opus 5 | $0.00022 | $0.00579 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
process 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process all unprocessed notes in inbox/raw/, then scan thinking/ for any notes ready to promote.
Part 1: inbox/raw/
For each .md file in inbox/raw/:
-
Read the content and analyze what it contains.
-
Detect domain — Check if content matches any registered domain in CLAUDE.md:
- High confidence (obvious match): suggest the domain
- Low confidence (unclear): ask the user to choose or create a new domain
- If no domains exist yet, ask user to create one first via the create-domain skill
-
Classify note type — Determine the
typefield:- concept, decision, reference, meeting, idea, note, belief, frame, lesson, model, goal, plan, research
-
Check for thinking content — If the content is primarily reasoning, a scratchpad, an open question, or ongoing research, offer to route to
thinking/instead ofinbox/ready/:- "This looks like a thinking note (reasoning/research/scratchpad). Move to thinking/ with
status: thinking?" - If yes:
git mv inbox/raw/[file] thinking/[YYYY-MM-DD-topic].md, setstatus: thinking, skip remaining steps for this file - If no: continue to step 5
- "This looks like a thinking note (reasoning/research/scratchpad). Move to thinking/ with
-
Check for multi-topic content — Scan for structural signals that the note covers 3+ independently page-worthy topics (each self-contained and useful on its own without the others):
- 3+ H2 (
##) sections with clearly different subjects [fact]/[idea]blocks that are clearly unrelated and independently meaningful
Only flag if topics are genuinely separable — not if sections are tightly related and better understood together. If detected, add a visible notice:
"This note covers [N] independently page-worthy topics. When you run
/distribute, you'll be offered to split it into separate pages." - 3+ H2 (
-
Generate frontmatter — Add full YAML frontmatter:
--- name: "[descriptive_kebab-case_name]" domain: "[detected-domain]" origin: braindump type: "[detected-type]" status: unprocessed description: "[~150 char summary]" tags: [] date: "[original date from raw note, quoted string]" created: "[original date from raw note, quoted string]" last_updated: "[today, quoted string]" --- -
Preserve original source — Before any transformation, capture the entire raw content in a collapsible callout at the bottom of the note:
> [!quote]- Original Source > [verbatim raw text, exactly as captured, no formatting changes]The processed/transformed content lives above this callout as the main body. The callout is collapsed by default so it doesn't clutter reading, but the original is always available for reference.
-
Preserve observation categories — Keep any
[fact],[idea],[decision], etc. syntax from the raw capture. -
Move to inbox/ready/ — Use a two-step process to move and update status: 9a. Move the file:
bash mv inbox/raw/[filename] inbox/ready/[filename](Use plainmvfor untracked files,git mvif tracked) 9b. Editinbox/ready/[filename]: changestatus: unprocessed→status: ready -
Update brain/QUEUE.md — Record or update the note's processing state:
- If the note path is not already in the table: append a new row with Stage
ready, today's date, and any relevant notes. - If the note path already exists (e.g., it was previously in the queue as
raw): update the Stage field toreadyand update Last touched.
| inbox/ready/[filename] | ready | YYYY-MM-DD | — | - If the note path is not already in the table: append a new row with Stage
-
Report for each note:
- Original filename
- Detected domain + type
- Generated description
- New location in
inbox/ready/(orthinking/if rerouted)
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 · 105 lines · 44 tokens per session scan A 6a3ff103d9f7
process is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 1,158 once invoked, about $0.0002 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-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
ingest
Ingest a source (URL/file/text) into Raw Sources + compile 1015 Wiki pages, with mandatory user-purpose gate and mothership cross-linking.
audit
Audit the whole Wiki vault against 3 knowledge-integrity criteria — eligibility coverage, MOC-cluster consistency, confidence calibration. Produces a vault health report and queues high-priority pages for /verify.
verify
Verify a single Wiki page against 3 knowledge-integrity criteria — eligibility, consistency, confirmability. Writes verificationStatus back to the page; flags conflicts as disputed rather than deleting them.
lint
Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).
onboard
Interview-based first-run setup for this LLM Wiki kit. Asks the essential questions (vault location/name, Mode A/B, mothership path, Core Context identity + reuse axes), then fills every placeholder and writes Core Context so the wiki knows you from day one. Activate when the user says "온보딩해줘", "처음 시작할게", "처음 시작"…