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/the-sid-dani/second-brain-os/findnpx skills add the-sid-dani/second-brain-os --skill findgit clone --depth 1 https://github.com/the-sid-dani/second-brain-osWrote 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/skills/the-sid-dani/second-brain-os/find)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/find"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/find.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.00150 | $0.02382 |
| Opus 5 | $0.00075 | $0.01191 |
| Sonnet 5 | $0.00030 | $0.00476 |
| Haiku 4.5 | $0.00015 | $0.00238 |
Grade A, and why
find 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
find
Unified recall across the second brain. Default mode: ranked list of matches. Optional: synthesis pass that reads top matches and produces a citations-backed summary.
Before you begin: read the Configuration section in root CLAUDE.md. Path tokens like <workspace.resources> resolve from there — don't hardcode.
Why this exists
Without /find, recall is manual flailing across four organizational locations: Resources (research/reference/meetings), Projects (active), Archive (closed), and Memory (daily logs + curated long-form). /find unifies the search surface into one skill.
Two downstream consumers depend on this:
- Layer 3 skills (briefing, meeting-prep, etc.) — before generating "what's on your plate today", they need to ask "what existing notes are relevant?". Without a recall primitive, every Layer 3 skill reinvents search.
- The user, daily — "do I have anything on the Anthropic admin API?" should be one slash command, not a 4-step
find | grep | head | catritual.
This skill is a port of claudesidian's research-assistant adapted to our paths, frontmatter conventions, and the synthesis-with-citations pattern. The "identify contradictions" guidance from claudesidian is preserved — when sources disagree, surface it explicitly rather than silently pick one.
When to use
Trigger phrases (broad — recall is the pattern, not the literal command):
- "do I have anything on X" / "what do I have on X"
- "find my notes on X" / "search for X"
- "is there research on X" / "any research about X"
- "what did I save about X" / "what do I know about X"
- "is there a project for X" / "any project related to X"
- "what's in my notes on X" / "search my second brain for X"
- "/find X" / "/find"
Do NOT trigger for:
- Content creation — generate directly. Recall is implicit; the user will say "find" if they want it first.
- A specific known filename — Read it directly.
- Web search — use
WebSearch/WebFetch. - Code search inside
<workspace.coding>/<repo>/— that's a per-repo concern;/finddoesn't span gitignored code repos.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 205 lines · 150 tokens per session scan A 139257935c88
find is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 28d ago), licensed MIT. It adds 150 tokens to every session and 2,382 once invoked, about $0.0007 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
follower-onboard
Onboard a NEW family/team machine as a FOLLOWER-CONSUMER joining the multi-machine Claude+vault network. A follower READS the shared vault + canon + skills + memory as RECEIVE- ONLY data, runs nothing heavy locally (no RAG/reindex/GPU), and the hub never pushes executable hooks to it. Trigger on "/follower-onboard "…
claudeai-sync
One-command incremental sync of a claude.ai WEB account into the Obsidian vault — pull only new/changed chats, fold them in as notes (idempotent, never overwrites curated ones), extract artifacts as first-class notes, concept-link the new artifacts, refresh the RAG index + dashboard. Trigger on "/claudeai-sync", "pull…
chat-search
Search INSIDE past Claude Code sessions (the episodic "book of chats" index) — find which previous session discussed a topic, and continue it with one command. Uses a SEPARATE session index, NOT the curated-knowledge RAG, so raw chat noise never pollutes the distilled brain. Trigger on "/chat-search", "which chat…
five-hard
Five Hard Questions — monthly (or on demand) the second brain ITSELF asks the owner 5 hard questions about their own long-held beliefs and codex entries that haven't been revisited in a while. Prevents assumptions from fossilizing. Trigger on "/five-hard", "challenge my beliefs", "pressure-test my views". Part of the…
intake
Rule intake: one pass routes a new rule/preference/policy edit into ALL the right homes (always-loaded canon, memory, the behavioral Bible, a skill, a hook) and leaves a trace in the always-loaded layer so parallel processes see it on their own. Trigger on "/intake", "record this rule", "route this to its homes".…
canon-revision
Full structural REVISION of an always-loaded rules file (CLAUDE.md / MEMORY.md): build a TOP block of the most important rules + numbered categories, move rule bodies verbatim (a script moves bytes and proves 0 losses; the LLM decides only the mapping), fold heavy mechanics into trigger+gist+pointer form, then guards…