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/generalgit clone --depth 1 https://github.com/superuser-pal/awesome-second-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/commands/superuser-pal/awesome-second-brain/general)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/general"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/general.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.00034 | $0.00560 |
| Opus 5 | $0.00017 | $0.00280 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
general 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 3d 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.
What it actually says
Capture the following input.
-
Determine capture type from content:
- Braindump: Free-form thoughts, ideas, observations
- URL: If content contains a URL, use
defuddle parse <url> --mdto extract clean markdown - Document reference: If a file path (absolute or relative) or specific location is provided, read the file, extract its contents, and summarize into the capture note.
-
Determine destination — ask the user (or infer from content if obvious):
- Inbox (default): ideas, facts, URLs, braindumps to be classified later →
inbox/raw/ - Thinking: reasoning, scratchpads, open questions, ongoing research →
thinking/
- Inbox (default): ideas, facts, URLs, braindumps to be classified later →
-
Create the capture note with
status: unprocessed(inbox) orstatus: thinking(thinking):Inbox (
inbox/raw/[topic]-[YYYY-MM-DD].md):--- date: "[today]" created: "[today]" status: unprocessed ---Thinking (
thinking/[YYYY-MM-DD-topic].md):--- date: "[today]" created: "[today]" status: thinking tags: - thinking --- -
Structure content with observation categories where natural:
[fact]— Objective, verifiable information[idea]— Subjective concepts, hypotheses[decision]— Commitments, choices made[technique]— Methods, processes, tactics[requirement]— Constraints, dependencies[question]— Open inquiries to investigate[insight]— Realizations, pattern recognition[problem]— Issues, pain points[solution]— Fixes, workarounds[action]— Task items
Syntax:
- [category] contentDon't force categories — if the input is simple or short, plain text is fine.
-
Report what was captured and where it was saved.
-
Remind: For inbox captures, run
/processto add frontmatter and classify, then/distributeto promote to a page. For thinking captures, use/processwhen ready to promote.
Content to capture: $ARGUMENTS
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.
- 3d ago First seen · 60 lines · 34 tokens per session scan A fcd1d0e7fb67
general is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 560 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 "온보딩해줘", "처음 시작할게", "처음 시작"…