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/new-projectnpx skills add the-sid-dani/second-brain-os --skill new-projectgit 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/new-project)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/new-project"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/new-project.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.1 | $0.00069 | $0.05280 |
| Opus 5 | $0.00034 | $0.02640 |
| Sonnet 5 | $0.00014 | $0.01056 |
| Haiku 4.5 | $0.00007 | $0.00528 |
Grade A, and why
new-project 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-project
Scaffolds any new project — <assistant.name> meta-project OR Area-owned app repo. The two cases share 90% of the logic; the differences (folder location, git init, GitHub repo, app manifest) live in a single branch on the project-type question.
Before you begin: read the Configuration section in root CLAUDE.md. All paths, the user's name, and their GitHub username come from there. Throughout this skill, references like <workspace.projects> and <user.github> resolve to whatever's defined in that section. Don't hardcode.
Why this exists
Per-project YAML frontmatter is the source of truth for project discovery. Every new project must start with that frontmatter populated correctly, or /prune-projects and frontmatter queries break. Doing this by hand is error-prone — date prefix, status field, project-type enum, template selection, and (for code) GitHub remote setup all need to be right. This skill makes the happy path one command.
OKF structure (Pass 7, 2026-06-28 — corrected same day): every non-code project scaffolds a machine-generated index.md alongside CLAUDE.md + memory.md. The index is a derived view of frontmatter — never hand-edited — so it doesn't violate the "no static INDEX" rule (decision #15, amended #15a to permit machine-generated indexes). It answers "what exists here", the fix for ad-hoc file recreation. Do NOT pre-create folders — no forced inputs//working//outputs/ base-3 (that lifecycle scaffold was repealed; it's not part of OKF, which organizes by concept). Per C10, concept folders emerge as the project's content arrives, named for what they hold.
Code projects fold into this skill rather than living in a separate /new-code-project because the shape is the same: a folder with CLAUDE.md + memory.md + status frontmatter. New app repos live under the owning Area's apps/ subtree, initialize their own git, optionally create a GitHub remote, and carry app.manifest.json for discovery. <workspace.coding>/ is grandfathered for existing repos only.
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 · 354 lines · 69 tokens per session scan A ea8f995c90e6
new-project is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 5,280 once invoked, about $0.0003 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
dr-fanout
One command to fan a Deep Research prompt out to several external LLMs at once (ChatGPT / Gemini / Grok / others) through the operator's logged-in browser, then collect the reports, archive the originals, and synthesize a consensus. Trigger on "/dr-fanout", "fan out the DR", "distribute the research prompt". Automates…
fb-reply
Read who commented on the owner's recent Facebook posts and post PERSONALIZED replies through their real logged-in Chrome (live-tab, low-ban-risk), draft-first and rate-limit-guarded. Trigger on "/fb-reply", "reply to my facebook comments". Replying on your OWN posts is expected behavior; the guard enforces a daily…
journey
Resurrect and continue a build-in-public BOOK — the serialized story of a founder + AI- cofounder journey. One command: pick up state (which days are written in which languages, what's uncommitted, where the gaps are), then continue writing via the established pipeline. Trigger on "/journey", "the book", "continue the…
3
Launch autonomous multi-machine consensus between Claude peers (hub + laptops + teammate machines): the peers negotiate a decision among themselves over a shared coordination channel and execute it, without using the human as a courier. Trigger on "/03" or phrases like "work it out among yourselves" / "find…
alfa-search-recall-deepresearch
Mandatory decision protocol ("Alpha Protocol") for any new STRATEGIC work — never jump to implementation on local recall alone. Run RECALL over the knowledge vault → GAP analysis → emit a DEEP RESEARCH PROMPT to run in external deep-research tools → SYNTHESIS + Decision Memo when results come back. Trigger on…
follower-onboard
Onboard a NEW family/team machine as a FOLLOWER-CONSUMER joining the multi-machine Claude+vault network. A follower READS the shared vault + canon + skills + memory as RECEIVE- ONLY data, runs nothing heavy locally (no RAG/reindex/GPU), and the hub never pushes executable hooks to it. Trigger on "/follower-onboard "…