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/new-project/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/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/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/new-project"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/new-project.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.00116 | $0.06387 |
| Opus 5.5 | $0.00046 | $0.02555 |
| Sonnet 5.5 | $0.00023 | $0.01277 |
| Haiku 4.5 | $0.00012 | $0.00639 |
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 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-project
Scaffolds any new project: a PROJ- project, a COD- project for code still being built, or a repo for a shipped app that an existing Area owns. They share most of the logic; the differences (folder location, git init, GitHub repo, app manifest) live in one 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: every project under <workspace.projects>/ scaffolds a machine-generated index.md alongside CLAUDE.md + memory.md. The index is a derived view of frontmatter and is never hand-edited. It answers "what exists here", the fix for ad-hoc file recreation. Do NOT pre-create folders: no forced inputs//working//outputs/ layout (OKF organizes by concept, not lifecycle). Concept folders emerge as the project's content arrives, named for what they hold (see the naming conventions in root CLAUDE.md).
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 code starts as a COD- project (the code-effort type): the project folder holds the plan, notes and outputs, and the code lives in the project's own ignored app/ (<workspace.project_apps>). Once an app ships and an Area owns it, it moves to <workspace.area_apps>; the code-repo type scaffolds that kind of Area-owned repo directly, with its own git, an optional GitHub remote, and an app.manifest.json for discovery.
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 · +26 lines · +47 tokens per session 2161413c4620
- 1mo 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 (3 stars, last pushed 7d ago), licensed MIT. It adds 116 tokens to every session and 6,387 once invoked, about $0.0005 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
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.
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
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.
issue-match
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers…
local-engineer-outreach
An engineer-outreach workflow that manages ongoing conversations with engineering contacts and moves them through planned next steps toward an invitation or call to action.
outbound-gate
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.