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/briefingnpx skills add the-sid-dani/second-brain-os --skill briefinggit 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/briefing)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/briefing"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/briefing.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.00289 | $0.10382 |
| Opus 5 | $0.00144 | $0.05191 |
| Sonnet 5 | $0.00058 | $0.02076 |
| Haiku 4.5 | $0.00029 | $0.01038 |
Grade A, and why
briefing 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
briefing
The chief-of-staff morning brief. Probes which signal sources are available, composes only the ones present, and assembles a single structured document at <workspace.root>/<workspace.resources>/briefings/morning-briefing-YYYY-MM-DD.html. Applies the user's priority signals, surfaces what needs them today, and recommends what to ship from each active project. Closes with a "Tools used" footer section transparently listing what was composed vs what was not configured — fork users with zero MCPs still get a useful brief from workspace state alone.
Before you begin: read the Configuration section in root CLAUDE.md. Path tokens like <workspace.resources> and <scripts.project_query> resolve from there — don't hardcode.
Progressive disclosure — load on demand:
references/html-composition.md— full Step 9 HTML spec (DOM scaffold, canonical color fallbacks, hard rules, voice, section-omission, pre-Write assertions). Load before composing the HTML.references/output-format.md— the stable DOM contract (fixed section order +data-od-idslugs + gating behavior).references/failure-modes.md— symptom → cause → fix table for every known failure.
Why this exists
<user.name> wants <assistant.name> to be a chief-of-staff, not a search engine. The morning brief is the single highest-value moment of the day: cross-referencing whatever signal sources are configured (email, calendar, messaging, issue-tracking, code-hosting) + project state to surface what actually needs attention vs what's noise. Before this skill, that ritual was a 4-tab manual scan that took 15 minutes and missed half the signal — and worse, didn't connect it to the active projects' plans.
/briefing is the answer to "Morning <user.name>, here's the lay of the land — and here's what to ship today." Its mandatory floor runs with zero external tools: read the active-projects index, tail each project's memory.md, read USER.md priority signals, read contacts. Its optional composition layer uses whatever's configured — gws gmail +triage / gws calendar +agenda via Bash (if gws CLI is installed), mcp__slack__* (if Slack MCP is authorized), mcp__atlassian__* (if Atlassian MCP is authorized), gh pr list (if gh CLI is installed), /find (always present, optional last step). Step 0.5 detects what's available at runtime; Step 0.6 probes auth health on each detected tool and pauses via AskUserQuestion if any are errored (so dead tokens are caught before the brief is composed, not after); later steps gate on the post-probe map.
What ships with it
5 files 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 · 492 lines · 289 tokens per session scan A ec06cc87ce3f
briefing is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 29d ago), licensed MIT. It adds 289 tokens to every session and 10,382 once invoked, about $0.0014 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…