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/r007b34r/opencode-obsidian-knowledge-workflow/connection-reviewnpx skills add r007b34r/opencode-obsidian-knowledge-workflow --skill connection-reviewgit clone --depth 1 https://github.com/r007b34r/opencode-obsidian-knowledge-workflowWrote 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/r007b34r/opencode-obsidian-knowledge-workflow/connection-review)<a href="https://agentmods.dev/skills/r007b34r/opencode-obsidian-knowledge-workflow/connection-review"><img src="https://agentmods.dev/badge/skills/r007b34r/opencode-obsidian-knowledge-workflow/connection-review.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.00060 | $0.01121 |
| Opus 5 | $0.00030 | $0.00561 |
| Sonnet 5 | $0.00012 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
connection-review 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
connection-review
Constraints
- NEVER scan whole vault; scope = 5-15 primary notes + small supporting set
- NEVER treat keyword overlap alone as evidence of connection
- NEVER synthesize week-level meaning (that is weekly-synthesis)
- NEVER write links without explicit user confirmation
- NEVER turn review into whole-vault graphing
Trigger Boundary
Use when: find note connections, suggest wikilinks, identify repeated patterns, surface contradictions, review relationships in a bounded set.
Do NOT use for:
- Raw inbox sorting →
inbox-triage - Week-level thesis and one action →
weekly-synthesis - Vault system health diagnosis →
vault-health-feedback - Upgrading material into stable notes →
note-promotion
Boundaries
- Owns: link discovery, pattern detection, contradiction surfacing, follow-up suggestions
- Delegates to:
note-promotion(follow-up accepted),weekly-synthesis(patterns span week) - Never absorbs: inbox routing, synthesis, health diagnosis, context maintenance
Continuations
| Condition | Next skill |
|---|---|
| Follow-up note suggestion accepted by user | note-promotion |
| Patterns span full week window, user requests synthesis | weekly-synthesis |
| Notes too raw for relationship analysis | inbox-triage |
| All connections weak/uncertain | Escalate to human |
Companion Skill
All vault operations follow obsidian-mcp. Forbidden: obsidian_patch_note, obsidian_append_to_note. Verify every write through readback.
Procedure
Phase 1: Scope
obsidian_list_notesorobsidian_search_notes→ identify recent/specified set- Bound to 5-15 primary notes; reject unbounded requests (ask user to narrow)
Phase 2: Read
- For each:
obsidian_get_note format:"document-map"→ structure overview format:"content"only when evidence is needed for a specific connection- Read older notes only to verify a suspected relationship
Phase 3: Analyze
When analyzing, read references/examples.md for connection quality calibration.
What ships with it
6 files 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.
- 5d ago First seen · 122 lines · 60 tokens per session scan A 6a17dacfb269
connection-review is a skill published in the GitHub repository r007b34r/opencode-obsidian-knowledge-workflow (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,121 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-08-31.
Other skills, from other repositories
project
Create or maintain an Architecture Studio project — initialize its record bundle, remember sourced facts, capture or supersede decisions, inspect project status, or migrate a 1.x PROJECT.md. Use when the user says “set up the project,” “remember this,” “we decided,” asks about project context, or runs /as:project.
llm-wiki
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…
cc-wiki
Distill the user's /.claude history into a Quartz knowledge base. Runs preprocess.py, dispatches parallel project-digest agents, then parallel cross-cutting synthesis agents (people / companies / projects / concepts / workflows / tools / playbooks), writes the spine, installs Quartz, and starts the dev server. Single…