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/tonydzi/second-brain-starter-kit/episodenpx skills add tonydzi/second-brain-starter-kit --skill episodegit clone --depth 1 https://github.com/tonydzi/second-brain-starter-kitWrote 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/tonydzi/second-brain-starter-kit/episode)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/episode"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/episode.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.00093 | $0.01783 |
| Opus 5 | $0.00046 | $0.00892 |
| Sonnet 5 | $0.00019 | $0.00357 |
| Haiku 4.5 | $0.00009 | $0.00178 |
Grade A, and why
episode 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EPISODE_ADAPTER (stage S5 of content factory v2 — the contract [[decision-content-pipeline-reality-show]] §7.2)
GOAL: ONE source post → an "episode" = one draft PER (tier × platform) from §7.2, with cross-links downward and canonical→GitHub baked in. Draft-first: we write drafts and publish NOTHING.
THE §7.2 CONTRACT (implemented 1:1):
tier length platforms (phase 1) language voice/model
teaser 240-370 (HARD) RU channel · X (EN) RU TG/EN X authorial · Opus
medium 800-2500 Facebook (RU) RU authorial diary · Opus · LINK IN THE 1ST COMMENT (not in the body) + a question
longread 4000+ narrative RU channel·VC.ru·Habr(RU) · GitHub(EN) RU and EN authorial reality-show · Opus
dev-log a dry log GitHub (EN, canonical) EN technical, impersonal · Sonnet scaffold + Opus for cohesion
- The owner's voice (
authorial) = Opus ONLY. The dev-log is not authorial — Sonnet assembles it, Opus stitches it together. - canonical = the GitHub markdown on every platform (a single source of truth for AI). Repo:
github.com/tonydzi/clawrush. - NO copy-paste — every file is a NATIVE rewrite for its platform.
- Cross-links downward: teaser→longread; medium→longread (in the 1st comment); longread ←teaser →dev-log; dev-log→longread + an anchor to our Deep Research.
- THE PLATFORM DECIDES THE LANGUAGE (there is no bilingual pair on every tier).
- The S3 narrative ([[style-reality-show]]) by tier: teaser=cold open+cliffhanger; medium=a full episode arc; longread=an extended episode+recap; dev-log=raw material, no drama.
- The cofounder CTA (medium+longread, the owner's rule, memory [[cofounder-cta-public-contact]]): WhatsApp +1 341 222 9178 = an authorized PUBLIC contact (a privacy carve-out), never strip it.
- VC.ru + Habr (the RU geo longread) = phase 1 since 2026-07-04 (the style files
_STYLE-vcru.md/_STYLE-habr.mdare written and live incontent-factory\; the writer loads them by the pointer in the placeholder). PHASE 2 (deferred): onlyReddit(the EN geo dev-log) — scaffolded with the--with-phase2flag.
PATHS:
- ⭐ FACTS AND CONTINUITY (v2, 2026-07-10) = THE SINGLE CANON
$OBSIDIAN_VAULT/04-Projects\show-canon\: before assembling an episode, read the anchor beat (beats\) plus its arcs/loops — "previously on the show", the cliffhanger and the season question come FROM THERE (not from memory, not from SHOW-STATE, which is frozen). Respect the beat'srevealaxis: don't burn live_hold/spoiler_until. Pick the next move with/reality-show next. After publishing — write the consequences back into the beat + runcanon_render.py. - Source material:
$IMPORTS_ROOT/content-factory/triage/posts.md(📝) — or a topic the owner names. - The scaffolder (deterministic, 0 tokens):
$IMPORTS_ROOT/content-factory/episode_adapter.py. - Bundles:
episodes\<slug>\(8 .md files in phase 1 / 9 with--with-phase2+ meta.json; every §7.2 field is baked into the placeholders). - Style: [[style-reality-show]] (
08-Templates\style-reality-show.md) +04-Projects\personal\facebook-diary-auto\_STYLE.md+ [[style-Mei-influence]] + the golden corpus up to 2023.
STEPS:
- PICK the topic: if the owner named one, use it; otherwise show the 📝 items from
posts.mdand take the strongest thread. Runlistbeforenew. - SCAFFOLD:
python episode_adapter.py new --slug <kebab> --title "<title>" --source "hub:<id>"(+--with-phase2for VC.ru/Habr/Reddit) → a bundle of empty drafts + meta.json. - WRITE (the model is named in each placeholder): teaser-ru/en, medium-fb (the body WITHOUT the link + a "1ST COMMENT" block), longread-ru/en, devlog. Replace the stubs, leave the hint comments in place. Privacy is strict (the only carve-out is the cofounder's WhatsApp).
- CHECK (the visibility layer):
python episode_adapter.py check --slug <slug>— lengths (a teaser outside 240-370 = HARD FAIL; medium/longread = WARN), CTA present, empty files. Only FAIL=0 → step 5 (a WARN on an unfinished longread is acceptable until it is written out). - REVIEW (draft-first):
set-status --slug <slug> --status review; into Telegram Saved (chat_id<YOUR_CHAT_ID>, account "work_acct_a", no parse_mode): "🎬 Episode '' — the per-tier drafts are ready (check ✅). episodes<slug>. Say 'publish' and I'll lay them out." NOTHING goes outward. - EXPORT TO PUBLISHING — only on the owner's explicit "publish"/"+" (Tier-2):
python episode_adapter.py export --slug <slug>→drafts\episode-<slug>.md(formattype: content-factory-draft+ the registers## -> TG/X/FB). From there the EXISTING path:content_approve.py --serve→content_publish.py(→ Saved; the real channels are Phase 2b/Tier-2). GitHub/Reddit/VC.ru/Habr are published MANUALLY (gh / natively), not through content_publish. We do NOT breed a second publisher.
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 · 67 lines · 93 tokens per session scan A 6174b04d6a6f
episode is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (5 stars, last pushed 6d ago), licensed MIT. It adds 93 tokens to every session and 1,783 once invoked, about $0.0005 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
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…