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/setup-contextgit 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.00024 | $0.01684 |
| Opus 5 | $0.00012 | $0.00842 |
| Sonnet 5 | $0.00005 | $0.00337 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
setup-context 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-context
Guided onboarding wizard for Awesome Second Brain. Choose a level:
Level 1 — Health Check (Is everything wired up?)
Level 2 — First-Use Setup (Get the vault ready for work)
Level 3 — Power Setup (Explore the full system)
Ask the user which level they want before starting. Default to Level 2 for brand-new installs.
Level 1 — Health Check
Safe to re-run at any time. Verifies the install is correct without making changes.
1.1 Vault Structure Check
Confirm all required top-level vault folders exist:
brain/dashboards/inbox/(withraw/andready/subdirectories)domains/plan/work/thinking/
For each folder, print ✅ if it exists or ❌ with a fix instruction if it's missing.
1.2 Hook Dependency Check
Confirm Bun hook dependencies are installed:
- Check that
.claude/scripts/node_modules/exists - If missing: tell the user to run
npm run setupfrom the vault root (orcd .claude/scripts && bun install)
1.3 Hook Registration Check
Confirm the hook scripts are active by looking for evidence of the session-start hook having fired in the current session context. Also check:
settings.local.jsonexists at vault root- It contains references to
session-start.sh,classify-message.ts,validate-write.ts,pre-tool-use.ts
If settings.local.json is missing: tell the user to re-run install.sh (Mac/Linux) or install.ps1 (Windows).
1.4 NORTH_STAR Check
Check if brain/NORTH_STAR.md exists and is not empty (beyond template comments).
- If empty or only template text: note that Level 2 setup will fill it in.
1.5 Health Report
Print a final ✅/❌ summary table. Example:
✓ Vault structure all 7 required folders found
✓ Hook dependencies node_modules present
✓ Hook registration settings.local.json configured
✗ NORTH_STAR.md not filled in — run Level 2 to complete setup
1 issue found. Run /setup-context and choose Level 2 to resolve it.
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 · 190 lines · 24 tokens per session scan A 9fceb83930b3
setup-context is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,684 once invoked, about $0.0001 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 "온보딩해줘", "처음 시작할게", "처음 시작"…