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/migrate-worknpx skills add the-sid-dani/second-brain-os --skill migrate-workgit 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/migrate-work)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/migrate-work"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/migrate-work.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.00130 | $0.03278 |
| Opus 5 | $0.00065 | $0.01639 |
| Sonnet 5 | $0.00026 | $0.00656 |
| Haiku 4.5 | $0.00013 | $0.00328 |
Grade A, and why
migrate-work 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate-work
Pulls your existing work into your PARA workspace. The signal is your past Claude Cowork sessions (stored locally on your Mac) — not a blind scan of your folders. It reads what you've actually been working on, shows you the distinct projects it found, and — for the ones you pick — scaffolds clean PARA entries with a CLAUDE.md + memory.md, copying any real work files in (never moving them).
Why sessions, not a folder scan: your work could live anywhere; your Cowork sessions are the reliable record of what you actually do. Each session carries a title, a working directory, and a transcript — enough to recognize a project and seed its memory.
Hard invariants (DO NOT VIOLATE)
- M1 — COPY, NEVER MOVE. Originals are never moved, renamed, or deleted. Bring work in with
cp; the user's source folders stay exactly where they are. A move that loses someone's only copy of real work is unrecoverable. - M2 — DISCOVERY IS PURE READ. Phase 1 (enumerate sessions, read transcripts, scout-summarize) touches nothing on disk. No write happens before the approval gate. Every probe verb is read-only.
- M3 — ONE APPROVAL GATE. Exactly one human stop: the barrier between discovery and writes. Nothing is scaffolded or copied until the user explicitly selects items. Low-confidence/flagged items are never auto-applied.
- M4 — NO FABRICATION. Every discovered "project," summary, and seeded memory line traces to real session content. Never invent a project, a purpose, or a decision the transcript doesn't show. If a session is ambiguous, flag it for the user — don't guess. (Recency-derived metadata —
suggested_status, date range — is allowed ONLY as a LABELED inference confirmed at the approval gate; transcript-derived claims — summary, decisions, seed_memory — must be grounded in actual session content.) - M5 — CODE PLACEMENT. Runnable code stays in its existing standalone repository or, after the user identifies an owning Area, may be copied into
<workspace.areas>/<area>/apps/<app>/(ignored by the outer repo). NEVER copy runnable code into Projects, Resources, Inbox, or the grandfathered<workspace.coding>bucket. - M6 — NEVER AUTO-COMMIT. Writes create new files in the workspace; stop at the diff and surface a manual commit command. Never
git add/git commit.
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 · 148 lines · 130 tokens per session scan A 18ed90327961
migrate-work is a skill published in the GitHub repository the-sid-dani/second-brain-os (2 stars, last pushed 29d ago), licensed MIT. It adds 130 tokens to every session and 3,278 once invoked, about $0.0006 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…
oma-pm
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
oma-coordination
Guide for coordinating PM, Frontend, Backend, Mobile, and QA agents on complex projects via CLI. Use for manual step-by-step coordination and workflow guidance.
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…
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…