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/archive-projectnpx skills add the-sid-dani/second-brain-os --skill archive-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/archive-project)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/archive-project"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/archive-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.00229 | $0.02585 |
| Opus 5 | $0.00114 | $0.01293 |
| Sonnet 5 | $0.00046 | $0.00517 |
| Haiku 4.5 | $0.00023 | $0.00259 |
Grade A, and why
archive-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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
archive-project
Closes the loop on a project: appends a retrospective to memory.md (optional but encouraged), flips status: active → done in CLAUDE.md's YAML frontmatter, moves the whole folder to <workspace.root>/<workspace.archive>/<slug>/, then regenerates the parent Area's index.md. The project moves WHOLE — there is no artifact-promotion step (thin-Areas model, 2026-07-10: Areas hold rules + memory + a generated index only; archived projects stay discoverable via the Area index).
Before you begin: read the Configuration section in root CLAUDE.md. Path tokens like <workspace.projects> resolve to whatever's defined there — don't hardcode.
Why this exists
/prune-projects filters on the status field. A project that gets moved by hand without the status flip looks active forever — <assistant.name> can't tell it's archived. This skill makes the right thing the easy thing: one command, frontmatter and filesystem stay consistent, optional retro captures the "what did we learn" without forcing it.
The retro matters because the project's memory.md is the only durable record of the decision history. Once a project is archived, nobody re-reads its memory unless something breaks — so a one-paragraph "what worked / what didn't" entry at the end is high-leverage. But forcing it would make the user skip the skill entirely, which is worse. Make it cheap to opt in.
When to use
Trigger phrases (not exhaustive):
- "archive the X project"
- "I'm done with X"
- "wrap up X"
- "move X to archive"
- "X is finished — close it out"
- "shelve X for now"
- "clean up the X work"
Do NOT trigger for:
- Code repos under
<workspace.coding>/— those have their own git lifecycle; archive the repo manually (no dedicated skill for this). - Pausing a project — that's a status change to
paused, not an archive. Edit the frontmatter directly. - Deleting — never. Archive is move, not delete.
Process
The skill is interactive. The interactive prompts (AskUserQuestion) only fire when the user runs the skill themselves; subagent runs invoke with the answer pre-extracted from the prompt.
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 · 188 lines · 229 tokens per session scan A 7c0745776995
archive-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 229 tokens to every session and 2,585 once invoked, about $0.0011 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…
bus
Cross-machine messaging between computers in the fleet over a shared TELEGRAM GROUP (primary rail) — every machine posts/reads in one group via the Telegram MCP, so it works even when file sync is down, AND humans can watch the machines talk in plain sight. A synced folder stays as the FALLBACK for oversized payloads.…