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/briefing/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/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/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/briefing"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/briefing.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.00098 | $0.10576 |
| Opus 5.5 | $0.00039 | $0.04230 |
| Sonnet 5.5 | $0.00020 | $0.02115 |
| Haiku 4.5 | $0.00010 | $0.01058 |
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 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 — 504 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 — Gmail and Calendar connector tools (if a Google Workspace or Gmail/Calendar connector is connected), 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
3 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.
- 7d ago Changed · +12 lines · -191 tokens per session ef13c055879c
- 1mo 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 (3 stars, last pushed 7d ago), licensed MIT. It adds 98 tokens to every session and 10,576 once invoked, about $0.0004 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.