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/contactnpx skills add the-sid-dani/second-brain-os --skill contactgit 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/contact)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/contact"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/contact.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.00131 | $0.02993 |
| Opus 5 | $0.00066 | $0.01496 |
| Sonnet 5 | $0.00026 | $0.00599 |
| Haiku 4.5 | $0.00013 | $0.00299 |
Grade A, and why
contact 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 5d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contact
Entity-keyed recall for people. Fuzzy-match a name across <workspace.root>/<workspace.resources>/contacts/, surface the matched profile + last interaction + open commitments. Read-only.
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 /contact, recall about a person is a manual ritual: list the resolved contacts directory, guess the slug, and read the file. Focused briefing/meeting-prep flows would otherwise have to reimplement fuzzy matching every time.
/contact is the entity-keyed recall primitive. It pairs with /find (topic-keyed). Together they cover both axes of "what do I know about X?" — where X is either a thing or a person.
The contacts schema (frontmatter fields, body sections, status enum, WikiLinks pattern) is defined in <workspace.root>/<workspace.resources>/contacts/README.md — read that first if you need schema details. This skill references the schema; it does not reproduce it.
When to use
Trigger phrases (broad — entity recall is the pattern, not the literal command):
- "/contact " / "/contact"
- "who is ?" / "who is again?"
- "what's my context with ?" / "context on "
- "remind me about " / "tell me about "
- "do I have notes on ?" — when the target is a person, not a topic
- "what did I promise ?" / "what does owe me?"
Do NOT trigger for:
- Topic-keyed recall (research, projects, meetings) — that's
/find. Phrases like "do I have anything on ", "what do I know about ". - Specific known filename — Read it directly.
- Mutation — use
/contact-logfor interactions. Adding a profile or updating other fields requires a separately approved direct edit after reading the contacts README; this skill remains read-only. - A question explicitly typed as
/find <name>—<user.name>is overriding precedence; honor it.
Precedence vs /find
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.
- 5d ago First seen · 197 lines · 131 tokens per session scan A 35382616efda
contact is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 29d ago), licensed MIT. It adds 131 tokens to every session and 2,993 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
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…
gmail
Check / search / digest Gmail on demand across multiple mailboxes (personal / assistants / work) via the owner's own OAuth connector — no browser needed, 0 tokens for the raw pull. Trigger on "/gmail", "check mail", "any important emails", "find the email about ", "mail digest". Read-only by default; drafting/sending…
inbox
Check this machine's cross-machine mailbox — messages Claude on ANOTHER computer left for Claude here, via a file-synced bus folder (no couriers). Trigger on "/inbox", "check inbox", "messages from the other machine". Also the way to SEND a message to Claude on another machine. A session-start hook auto-shows new…
chatgpt-sync
On-demand pull of FRESH ChatGPT conversations into the Obsidian vault — the manual twin of the scheduled nightly sync. Incremental + idempotent (keyed by conversationid; never clobbers concept-enriched notes, never duplicates). Both entry points call the SAME orchestrator script (single source of truth). Trigger on…
coach
A daily AI coach — a forward-looking accountability + mirror loop grounded in the owner's FULL identity layer (the vault knows them better than anyone). Trigger on "/coach", "morning review", "evening review", "what should I do today", "keep me on track". Runs a MORNING kick (mirror → accountability → one rock →…
faaa-sync
On-demand pull of FRESH follow-up call notes from a dedicated Telegram group into the CRM layer of the vault. Incremental + idempotent (dedup by Telegram message id) — safe to re-run, never makes duplicates. Manual counterpart of the weekly scheduled sync; both call the SAME scripts (single source of truth). Trigger…