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 cyanheads/obsidian-mcp-server --skill techniquesgit clone --depth 1 https://github.com/cyanheads/obsidian-mcp-serverWrote 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/cyanheads/obsidian-mcp-server/techniques)<a href="https://agentmods.dev/skills/cyanheads/obsidian-mcp-server/techniques"><img src="https://agentmods.dev/badge/skills/cyanheads/obsidian-mcp-server/techniques/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/cyanheads/obsidian-mcp-server/techniques"><img src="https://agentmods.dev/badge/skills/cyanheads/obsidian-mcp-server/techniques.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.00487 |
| Opus 5.5 | $0.00032 | $0.00195 |
| Sonnet 5.5 | $0.00016 | $0.00097 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
techniques 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 17d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
- techniques — 100% identical, 0 lines differ
What it actually says
Overview
A directory of cross-cutting techniques for shaping what a handler returns and how a client retrieves it — patterns that don't belong to a single API surface. Each entry is a self-contained reference under references/: the problem it solves, when to reach for it (and when not to), and how to apply it with current framework primitives.
These are patterns, not new primitives — they compose tool(), output/format() shaping, ctx.state, and the existing helpers. Where a technique has (or will have) a dedicated helper, its reference says so and links the tracking issue.
Techniques
| Technique | Path | Use when |
|---|---|---|
| Outline-on-overflow | references/outline-on-overflow.md |
A single tool call returns one document-shaped payload too big to inline (e.g. a ~130KB record), and you want an honest section outline + a re-call contract instead of truncating. |
Adding a technique
One file under references/, one row above. A technique earns a place here when it's a reusable response/retrieval pattern that (a) spans more than one tool or server and (b) isn't already covered by an api-* reference. Keep the reference concise: problem → when-to-use → how-to with current primitives → helper status. Bump metadata.version on any change (skill-versioning policy).
Related
design-mcp-server— choosing the tool surface and output shapes up front.add-tool— thetool()builder,format()⟷structuredContentparity, matching response density to context budget.api-canvas—spillover(), the row-collection sibling of outline-on-overflow.
What ships with it
1 file 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.
- 17d ago Changed b73811e285c6
- 1mo ago First seen · 33 lines · 79 tokens per session scan A 8f01d620e53c
techniques is a skill published in the GitHub repository cyanheads/obsidian-mcp-server (700 stars, last pushed 17d ago), licensed Apache-2.0. It adds 79 tokens to every session and 487 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
widget-authoring
Author or edit ThinkEx widgets, which are self-contained interactive HTML blocks inside documents. Use when the user explicitly asks for a widget, asks for interaction or live computation, or wants a document visual that ordinary blocks cannot express.
pkm-session-end
Use when wrapping up a work session — creates devlog entry, captures undocumented decisions/research/debugging, audits link health of session work, and updates project index. Primarily used via the pkm-capture agent.
pkm-write
Use when writing to the vault — creating new notes (vaultwrite), editing existing notes (vaultedit, vaultappend, vaultupdatefrontmatter). Handles duplicate checking, link discovery, annotations, and index updates for new notes. Provides guidelines for modifications.
pkm-explore
Use when researching what the vault knows about a topic — performs graph + semantic exploration with gap analysis to map existing knowledge and find missing connections. Primarily used via the vault-explorer agent. Not for routine session-start context loading (hooks handle that).
triage-tasks
Use when you want to review and batch-update open vault task statuses for the current project or across all projects.
tackle-task
Use when starting work on a specific vault task, when a task title or path is mentioned, or when coming from triage output.