Borrowing it
Nothing to install: this file belongs to the-sid-dani/second-brain-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/the-sid-dani/second-brain-os/main/.agents/skills/contact-log/SKILL.mdgit 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-log)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/contact-log"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/contact-log/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/contact-log"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/contact-log.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00087 | $0.04242 |
| Opus 5.5 | $0.00035 | $0.01697 |
| Sonnet 5.5 | $0.00017 | $0.00848 |
| Haiku 4.5 | $0.00009 | $0.00424 |
Grade A, and why
contact-log 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 7d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contact-log
Write-mode entity-keyed mutation. Append a new interaction entry to a matched contact's ## Interaction log section, auto-bump last_interaction frontmatter. Append-only — never rewrites prior entries, never touches About / Recurring topics / Open commitments.
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-log, a contact file is a static address book — populated once, then frozen. The Chief-of-Staff function (track who said what when) needs interaction history to compound. Each conversation adds a line; over months that line-set becomes the answer to "what did I promise last time?" and "when did we last sync?"
/contact-log is the write counterpart to /contact (read). Together they make the contacts directory alive — entity-keyed read AND entity-keyed append, with the locked schema preserved across both.
The schema (frontmatter fields, body sections, WikiLinks pattern, status enum) 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 (write-mode signals — broad on purpose):
- "/contact-log " / "/contact-log"
- "log my 1:1 with " / "log my meeting with " / "log my call with "
- "append interaction with " / "record my chat with "
- "I just talked to " / "just spoke with , log it" / "had a sync with "
- "wrote/promised/agreed with — log it"
The verb is the signal. Read-mode verbs ("who is", "what's my context with", "remind me about", "tell me about") fire /contact instead. Mutation verbs ("log", "append", "record", "talked-to", "spoke with") fire this skill.
Do NOT trigger for:
- Read-only recall of a person — that's
/contact. Phrases like "who is X again?", "context on Y". - Scaffolding a brand-new contact or editing other profile fields — handle as a separately approved direct edit after reading the canonical contacts README. This skill only appends interactions.
- Writing to the daily log —
/contact-logdoes NOT touchmemory/YYYY-MM-DD.md. <user.name> writes the day's narrative to memory/ separately.
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.
- 7d ago Changed · -93 tokens per session 6f374a12d1fb
- 1mo ago First seen · 268 lines · 180 tokens per session scan A c3d4b4a4503c
contact-log is a skill published in the GitHub repository the-sid-dani/second-brain-os (3 stars, last pushed 7d ago), licensed MIT. It adds 87 tokens to every session and 4,242 once invoked, about $0.0003 per session on Opus 5.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
apply
A browser-based job application workflow for submitting applications through services such as Ashby, Greenhouse, Lever, and Hacker News. It uses prepared candidate information, answers, job links, and cover letters.
screenpipe-api
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved…
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
nsr
A routine for starting a new, visible coding-agent session automatically through a scheduled task, so it appears in the recent-session list without someone pressing a start button.
routine-opt
Audit and cut the cost of a machine's scheduled routines: measure tokens per run, pick a lever (cheaper model, split, lower frequency, shorter prefix, retire) and prove the saving with a before-and-after measurement. Use when background routines burn more than interactive work. Triggers: /routine-opt, /ropt, routine…
slot
Registry of reusable agent sessions and slot allocation: claim a free scheduled-task slot instead of creating a new session, set its prompt and fire time, and release it when done. Use when you need to spawn or reuse a visible background session.