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 skills add tonydzi/second-brain-starter-kit --skill precedentgit 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/precedent)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/precedent"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/precedent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/precedent"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/precedent.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.00982 |
| Opus 5 | $0.00032 | $0.00491 |
| Sonnet 5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
precedent 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 today.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/precedent — have we decided this already? (find the precedent before deciding)
Cheap insurance BEFORE a new structural choice or proposal: maybe there is already a verdict on this topic (accepted / rejected / deferred) — so we do not re-pitch something already declined, nor re-decide what is decided. This is the "RECALL before activity" rule applied to the DECISION layer.
What to pull up (cheap → expensive; stop as soon as you find it)
- The declined journal (first — the most frequent hit): memory
$USERPROFILE/.claude/projects/<project>/memory/declined-decisions.md— what was rejected or deferred, why in the owner's own words, andRevisit-if(the condition under which it can come back). - The accepted-decisions journal (vault): grep
$OBSIDIAN_VAULT/02-Decisions/(subfolders by domain) and anydecision-*files in the vault.grep -rinl "<topic/keywords>" "$OBSIDIAN_VAULT/02-Decisions" - The Bible (rules for all actors): grep
reglament-*/protocol-*in the vault — maybe a standing rule already closes the question. - Semantic top-up (if the exact grep is empty but the topic was clearly discussed): the
/askskill (RAG over the vault) — it catches phrasings grep missed.
What to give back to the operator
A short verdict, not a dump:
- A precedent EXISTS → what was decided · when · why · a link to the note. If it was REJECTED,
name the
Revisit-if: reopen ONLY if the condition is met, or explicitly as a trade-off ("there is no other way") — never silently re-pitch. - No precedent → say exactly that: "I found no decision on this" (after checking the RIGHT drive/folder —
an empty result is often "looked in the wrong place", not "no data"), and then go decide from scratch
(for strategic questions, via the Alpha Protocol
R+DR).
When to call it
- Before I propose a new field / script / structure / rule / automation (per
show-before-after). - When the operator says "I think we discussed this".
- At the start of the Alpha Protocol — as part of the RECALL step.
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.
- today First seen · 64 lines · 65 tokens per session scan A fa501984a621
precedent is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (6 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 982 once invoked, about $0.0003 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-09-09.
Other skills, from other repositories
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…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
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-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.