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/fanpx skills add tonydzi/second-brain-starter-kit --skill fagit 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/fa)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/fa"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/fa.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.00126 | $0.03365 |
| Opus 5 | $0.00063 | $0.01682 |
| Sonnet 5 | $0.00025 | $0.00673 |
| Haiku 4.5 | $0.00013 | $0.00336 |
Grade A, and why
fa 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 3d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fa — the post-call follow-up in the owner's voice
🧒 When reporting to a non-technical owner: finish with an "In plain words" block ([[eli5-always]]). Only in the message TO him — it never goes inside the follow-up itself.
Why: after a call a person stays warm for a few hours, no more. A follow-up is not the minutes of a meeting, it is one short move that advances the deal: prove you listened → lock down who does what and by when → ask a question that cannot be left unanswered.
Boundary vs neighbors: /intro = introducing two people; /telegram-lead-outreach = a cold first contact; /fa = after an actual call with someone who already knows you.
§1. The owner's voice — derived from 17 of his real messages (June–July 2026)
Source: his personal/default DMs + the 🤝 groups ": 1-on-1 with Tony", and the calls archive chat (<YOUR_CHAT_ID>).
How he writes with his own hand (four sampled threads, 06-26 to 07-27):
- lowercase, straight from the first line, no "Dear" and no "Hello sir";
- short paragraphs separated by a blank line, 1–3 lines each;
- colloquial contractions and live little words: "v much", "no worries", "fellow countryman!", "+++", "..." instead of a period;
- a hyphen
-, never an em dash—, and definitely no "— Palo Alto AI Research Lab" as a signature; - informal address, by first name, from the very first word;
- specifics instead of politeness: he names the artifact, gives the link, sets the date;
- honesty as a move: he volunteers what he does not have ("we have no latency numbers") — that is his signature trait, always keep it;
- ends with a question or a proposed exchange, never with "looking forward to your feedback";
- 0–2 emoji per message, on point (🙂 🙌), never in rows and never in a header.
The mandatory frame of a new follow-up (5 blocks, 60–120 words):
- the hook — one phrase proving you listened: his own thought/number/detail that he himself said. Not a summary, but "this is what stuck".
- what I did — something already done, with a link/fact. Past tense, not "I'll follow up shortly".
- what's on you — exactly one item, in his own words, with a deadline.
- the date of the next step — a concrete day and time, not "sometime this week".
- one open question — as the last line, so that an answer is obliged to come.
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.
- 3d ago First seen · 167 lines · 126 tokens per session scan A 3145ae156a3a
fa is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (5 stars, last pushed 4d ago), licensed MIT. It adds 126 tokens to every session and 3,365 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
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.
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…
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.