second-brain-os: Skill for Claude Code

.agents/skills/design-weekly-update/SKILL.md

design-weekly-update is a skill for Claude Code, Codex from the-sid-dani/second-brain-os. It costs 59 tokens per session (290 once invoked), scanned A, a copy of weekly-update, MIT.

A guide for creating a single-file HTML slide deck for a weekly team update. The deck covers completed work, current work, blocked work, important metrics, and requests for the following week.

In plain words
What is it for?
Use it to create a 6–8 slide update with a cover, headline, shipped items, work in progress, blockers, metrics, next-week asks, and closing slide, with keyboard or click navigation.
Why use it?
It gives weekly status information a repeatable slide structure that makes progress, blockers, and responsibilities easy to present.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is the-sid-dani/second-brain-os's own configuration. It tells Claude Code and Codex how to work on second-brain-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything second-brain-os configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/the-sid-dani/second-brain-os/main/.agents/skills/design-weekly-update/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/the-sid-dani/second-brain-os

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for design-weekly-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/design-weekly-update/github.svg)](https://agentmods.dev/skills/the-sid-dani/second-brain-os/design-weekly-update)
Your own site
<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/design-weekly-update"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/design-weekly-update/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.

agentmods 80×15 button for design-weekly-update

Your own site · 80×15
<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/design-weekly-update"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/design-weekly-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 290 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.00290
Opus 5.5 $0.00024 $0.00116
Sonnet 5.5 $0.00012 $0.00058
Haiku 4.5 $0.00006 $0.00029

Measured 1mo ago against content hash 3b1e61270f4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-weekly-update 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 1mo 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.

Origin

This is a copy

92% identical to weekly-update — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/design-weekly-update/SKILL.md · 31 lines

What it actually says

Weekly Update Deck Skill

Produce a single-file horizontal-swipe HTML deck for a weekly team update.

Workflow

  1. Read DESIGN.md.
  2. Identify squad name, week range, and audience (squad-internal vs cross-functional).
  3. Slides:
    1. Cover (squad + week + author + date)
    2. Headline (one sentence + one number that matters this week)
    3. What shipped (3–5 items, link-style affordance)
    4. In flight (3–5 items, owner avatars)
    5. Blocked (1–3 items + clear ask)
    6. Metrics that matter (1–2 inline charts)
    7. Asks for next week (named owners)
    8. Closing + thanks
  4. Arrow keys or click navigation. Each slide is 100vw wide.

Output contract

<artifact identifier="weekly-update-w42" type="text/html" title="Weekly Update — Growth · W42">
<!doctype html>...</artifact>
Files

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.

Changes

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.

  1. 1mo ago First seen · 31 lines · 59 tokens per session scan A 3b1e61270f4d

Subscribe to this mod's changes

design-weekly-update is a skill published in the GitHub repository the-sid-dani/second-brain-os (3 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 290 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to weekly-update, differing in 24 lines, and is treated as a copy.

Related

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.

tonydzi/second-brain-starter-kit · 66 tokens

rep-reply

Find live third-party GitHub issues and discussions on topics where you have real hands-on experience and artifacts, then reply with that experience to build reputation. Use when asked to answer people about your work, find threads matching your expertise, or reply with evidence from your own setup.

tonydzi/second-brain-starter-kit · 59 tokens

dr-fanout

Fan one deep-research prompt out to several external LLMs at once through a logged-in browser, then collect the reports, archive the originals and synthesize a consensus. Use at the final stage of a research protocol, instead of hand-pasting one prompt into N sites. Triggers: "/dr-fanout", "fan out the DR"…

tonydzi/second-brain-starter-kit · 83 tokens

cv-outreach

A daily workflow for carrying out scheduled outward-facing tasks, such as event registrations, messages to organisers, and public posts. It uses a browser identity carefully so actions are made from the intended account.

tonydzi/second-brain-starter-kit · 101 tokens

devrel-wave

A planned outreach process for contacting developer-relations and research staff at major AI laboratories through several available channels. Developer relations, often called DevRel, is the team that works with developers and outside communities.

tonydzi/second-brain-starter-kit · 134 tokens

peer-onboard

A procedure for bringing an outside lead or peer into a shared working setup, including their contact space, records, previous conversations, and ongoing session.

tonydzi/second-brain-starter-kit · 152 tokens