What is obsidian-pro?

A set of rules for organizing notes in Obsidian, an app for linking and managing plain-text notes. It uses callouts, metadata fields, tags, and links to make notes easier to browse and query.

Creating standardized notes, adding summaries and action sections, recording source and project details, and tracking note status with tags and metadata.

It imposes a consistent structure so notes can be categorized, searched, and used by Obsidian's database-like features.

obsidian-pro — Skill for Claude Code and Codex by turmyshevd

Install

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.

Any agent

npx skills add turmyshevd/openclawgotchi --skill obsidian-pro

Clone the repo

git clone --depth 1 https://github.com/turmyshevd/openclawgotchi

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/turmyshevd/openclawgotchi/obsidian-pro/github.svg)](https://agentmods.dev/skills/turmyshevd/openclawgotchi/obsidian-pro)

Your own site

<a href="https://agentmods.dev/skills/turmyshevd/openclawgotchi/obsidian-pro"><img src="https://agentmods.dev/badge/skills/turmyshevd/openclawgotchi/obsidian-pro/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/turmyshevd/openclawgotchi/obsidian-pro"><img src="https://agentmods.dev/badge/skills/turmyshevd/openclawgotchi/obsidian-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 734 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00028	$0.00734
Opus 5	$0.00014	$0.00367
Sonnet 5	$0.00006	$0.00147
Haiku 4.5	$0.00003	$0.00073

Measured 9d ago against content hash d80e07a3cfd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

obsidian-pro 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 9d 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.

gotchi-skills/obsidian-pro/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Obsidian Pro Guide (Gold Standard Edition)

Use these rules to make notes "Obsidian-native", structured, and part of a high-quality knowledge base.

1. Visual Structure (Callouts)

Semantic formatting is mandatory. Always use Obsidian Callouts:

> [!abstract] Abstract: Brief TL;DR or summary of the note.
> [!quote] Raw: Mandatory. Full original text from the user message. Do not truncate.
> [!info] Details: For additional context, metrics, or technical specs.
> [!todo] Actions: Detected tasks or next steps.

2. Note Properties (Gold Standard Frontmatter)

Every note MUST start with this exact YAML block. Metadata is critical for Dataview and organization.

---
id: "YYYY-MM-DD-HHMMSS"
type: "vault-note"
note_type: "memo"       # memo, research, plan, asset, issue, insight
created: "YYYY-MM-DDTHH:MM:SS"
source: "telegram"      # telegram, discord, system
project: "project-slug"
topic: "sub-topic"
status: "seedling"      # seedling (draft), budding (developing), evergreen (ready)
tags:
  - "type/memo"         # Hierarchical: type/*
  - "area/product"      # Hierarchical: area/*
  - "status/seedling"    # Hierarchical: status/* (must match status field)
---

3. Interconnection & Layout

Wikilinks: Connect everything. Use [[Project Hub Name]] or [[Topic Name]].
Linking Rule: Always link back to the Project Hub ([[projects/project-slug]]) and relevant Area ([[topics/sub-topic]]).
Folders:
- notes/: Main storage for atomic notes.
- projects/: Hub pages for specific projects (e.g., bitdive.md).
- topics/: Index pages for broad areas (e.g., product.md).
- attachments/: For images and files.

4. Cleaning & Refactoring

Hierarchical Tags: Never use flat tags like #memo. Always use #type/memo or #area/marketing.
Status Sync: Always ensure #status/* tag matches the status field.
Stability: Keep IDs and filenames stable. If renaming, update all backlinks.
No Duplicates: Check vault_search before creating. Extend existing notes if they cover the same core thought.

Read the full file on GitHub · 73 lines

Changes

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.

9d ago First seen · 73 lines · 28 tokens per session scan A d80e07a3cfd6

Subscribe to this mod's changes

obsidian-pro is a skill published in the GitHub repository turmyshevd/openclawgotchi (48 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 734 once invoked, about $0.0001 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-30.

Memory and context agentic-ai ai-tamagotchi e-ink-display openclaw openclaw-skills telegram-bot-ai-assistant

add-compact

Add /compact command for manual context compaction. Solves context rot in long sessions by forwarding the SDK's built-in /compact slash command. Main-group or trusted sender only.

sbusso/claudeclaw · 40 tokens

add-qmd

Add QMD (Query Markup Documents) as an advanced memory search backend. Upgrades the built-in grep-based memorysearch with hybrid BM25 + vector semantic search + LLM re-ranking. Fully local, no API keys needed. Triggers on "add qmd", "qmd memory", "semantic memory search", "upgrade memory".

sbusso/claudeclaw · 73 tokens

swmm-modeling-memory

Read historical Agentic SWMM experiment audit artifacts and summarize repeated assumptions, QA issues, failures, missing evidence, run-to-run differences, lessons learned, and controlled skill update proposals. Use downstream of swmm-experiment-audit when multiple audited runs exist or when a user asks for modeling…

Zhonghao1995/agentic-swmm-workflow · 79 tokens

obsidian-pro