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/prune-projectsnpx skills add the-sid-dani/second-brain-os --skill prune-projectsgit 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/prune-projects)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/prune-projects"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/prune-projects.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 | $0.00208 | $0.01747 |
| Opus 5 | $0.00104 | $0.00873 |
| Sonnet 5 | $0.00042 | $0.00349 |
| Haiku 4.5 | $0.00021 | $0.00175 |
Grade A, and why
prune-projects 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 4d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prune-projects
Friday-cadence cleanup of <workspace.root>/<workspace.projects>/. <assistant.name> proposes archive candidates, the user approves in one multiselect, the chain handles the rest.
Before you begin: read the Configuration section in root CLAUDE.md. Path tokens like <scripts.project_query> and <workspace.projects> resolve to whatever's defined there — don't hardcode.
Why this exists
Active projects rot if nobody triggers cleanup. A pure auto-move on a 90-day timer eats live work — projects in long planning phases look dead. So the design is: <assistant.name> does the detection (fast, deterministic, scriptable), the user does the judgment (a 30-second multiselect) once a week. No drift, no surprise mass-archives.
The two prerequisites are already shipped:
<scripts.project_query>— outputs the project table withdaysand aSTALEflag./archive-project— handles the per-project archive (status flip + folder move).
This skill is just the orchestration: query → filter → ask → chain.
When to use
Trigger phrases (intentionally broad):
- "what's stale?"
- "any stale projects?"
- "Friday review" / "Friday cleanup"
- "what should I archive?" / "prune projects"
- "review my projects" / "what can I clean up?"
- "anything I should close out?" / "what's gone cold?"
Do NOT trigger for:
- Archiving a specific known project — use
/archive-projectdirectly. - Asking about one project's status — just read its
CLAUDE.md. - Code repos under
<workspace.coding>/— different lifecycle, separate skill (TBD).
Process
Step 1: Run the query
bash <scripts.project_query> --tsv
The TSV output has these columns (tab-separated, no header):
slug status type created touched days flag
Parse it. If the script errors (missing dir, etc.), abort and tell the user.
Step 2: Filter stale candidates
A project is a candidate if any of these are true:
status == "active"ANDtype != "ongoing"ANDdays >= 90status == "paused"ANDdays >= 60status == "done"(any age — these slipped through/archive-projectsomehow and should be archived now)
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.
- 4d ago First seen · 164 lines · 208 tokens per session scan A af968adf91c8
prune-projects is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 28d ago), licensed MIT. It adds 208 tokens to every session and 1,747 once invoked, about $0.0010 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
issue-match
Measure a TARGET repository's queue + find a LIVE door (an open issue matching our artifact) BEFORE pushing a PR there. Trigger on "/issue-match", "is this repo worth a PR", "measure the queue", "find a live issue". Answers "knock here or skip": how many open PRs, how many of the last N closed ones were actually…
agenda
The operator's day at a glance, on demand — today's calendar plus what needs THEM personally (leads due, real humans awaiting a reply, deadlines) pulled from Calendar + Telegram, ranked. Trigger on "/agenda", "what's on today", "my agenda". READ-ONLY summary — it never sends or commits anything. Pairs with a…
pm
When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian…
harness-design
Design and build multi-agent harness architectures for long-running AI application development. GAN-inspired Generator-Evaluator pattern, Sprint Contract negotiation, context management, quality criteria calibration. Based on Anthropic Engineering patterns. Use when: "build a harness", "multi-agent architecture"…
backlog-capture
Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
yao-board
Kanban board and task query expert. ALWAYS invoke this skill when the user asks about boards, tasks, task status, or project progress. Do not guess task state — use this skill first.