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/auditgit 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/audit)<a href="https://agentmods.dev/commands/superuser-pal/awesome-second-brain/audit"><img src="https://agentmods.dev/badge/commands/superuser-pal/awesome-second-brain/audit.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.00000 | $0.02435 |
| Opus 5 | $0.00000 | $0.01218 |
| Sonnet 5 | $0.00000 | $0.00487 |
| Haiku 4.5 | $0.00000 | $0.00244 |
Grade A, and why
audit 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 4d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
When to use: After substantial sessions, after reorganization, or periodically to maintain vault health. For lighter end-of-session checks, use /close-day instead.
Usage
/audit
Subagents
This command orchestrates two subagents for deep analysis:
vault-librarian— orphan detection, broken links, frontmatter validation, stale notes, index consistencycross-linker— finds missing wikilinks, orphan notes, broken backlinks
Launch vault-librarian first for the structural audit, then cross-linker for link quality.
Workflow
1. Check Folder Structure
Verify the vault matches the expected layout:
dashboards/HOME.mdexistsbases/contains all.basefiles (none scattered elsewhere)work/01_PROJECTS/contains only notes withstatus: activework/07_ARCHIVE/2025/andwork/07_ARCHIVE/2026/contain onlystatus: completednoteswork/03_INCIDENTS/contains only notes taggedincidentwork/02_1-1/contains only 1:1 meeting noteswork/06_ORG/PEOPLE.mdhas a## [Name]section for each known personwork/06_ORG/TEAMS.mdhas a## [Name]section for each known teamtemplates/contains only template files (with{{placeholders}})thinking/is clean (no leftover drafts that should have been promoted)- Nothing unexpected at vault root (allowed:
CLAUDE.md,vault-manifest.json,CHANGELOG.md,CONTRIBUTING.md,README.md,LICENSE,.gitignore— no user notes;Home.mdlives indashboards/)
2. Check Indexes
Read and verify each index file:
dashboards/HOME.md— do embedded Base views reference existing Bases? Are quick links valid?work/INDEX.md— are active projects still active? Are completed items in the right section? Any missing notes?brain/MEMORIES.md— is the "Recent Context" section current? Any stale claims?work/06_ORG/PEOPLE.md— are roles and project assignments current?work/05_REVIEW/WINS.md— do PR counts and project descriptions match reality?brain/SKILLS.md— are all slash commands registered? Workflows still valid?
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.
- 4d ago First seen · 232 lines · 0 tokens per session scan A dcb4fb8456bb
audit is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,435 tokens. 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 "온보딩해줘", "처음 시작할게", "처음 시작"…