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/sistema2d/framecode-vibework/obsidian-markdownnpx skills add Sistema2D/FrameCode-VibeWork --skill obsidian-markdowngit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/obsidian-markdown)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/obsidian-markdown"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/obsidian-markdown.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.00016 | $0.00577 |
| Opus 5 | $0.00008 | $0.00289 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
obsidian-markdown 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian-compatible Markdown
Purpose
Create or normalize Markdown that remains valid under FCVW schemas while adding Obsidian-specific navigation only when the project uses it.
Use conditions
Use when the user requests Obsidian formatting, wikilinks, embeds, callouts, note properties, or graph-oriented wiki maintenance. Ordinary FCVW documentation uses portable Markdown by default.
Inputs
Target note, wiki/schema.md, taxonomy, source links, destination, current canonical page, and the project's decision on supported Obsidian syntax.
Non-responsibilities
- inventing sources, confidence, status, tags, or relationships;
- replacing FCVW frontmatter with a second tool-specific metadata block;
- converting all Markdown to wikilinks without retrieval value;
- embedding secrets, private files, or unstable absolute paths;
- rewriting unrelated historical notes.
Procedure
- Select the applicable FCVW schema and preserve one YAML frontmatter block at the file start.
- Check for an existing canonical page before creating a note.
- Preserve sources, status, confidence, and semantic meaning.
- Use ordinary Markdown links for portable repository navigation; add
[[wikilinks]]only when Obsidian resolution is configured and useful. - Add embeds, callouts, highlights, or Mermaid only when they materially improve retrieval or comprehension.
- Validate link targets, heading hierarchy, frontmatter, placeholders, and rendering in the supported mode.
Formatting rules
- FCVW schema values and controlled statuses come from
wiki/schema.md; this skill does not define competing values. - A note has one H1 and a logical heading hierarchy.
- Internal wikilinks use the vault-relative note path or canonical title consistently.
- Embeds use
![[note]]or![[note#heading]]only for stable reusable content. - Obsidian callouts use a supported type and retain readable quoted content in ordinary Markdown renderers.
- Mermaid nodes must not contain sensitive values; clickable node behavior is optional and project-configured.
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 · 63 lines · 16 tokens per session scan A ed88b8e2f5b0
obsidian-markdown is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (23 stars, last pushed 5d ago), licensed Apache-2.0. It adds 16 tokens to every session and 577 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.
Other skills, from other repositories
evaluate-pattern-adoption
Run or plan this repository's pattern-adoption evidence evaluation locally with signed-in Codex agents. Use when asked to refresh stale evidence, assess stable or exploratory patterns, evaluate one or all catalog patterns, discover possible new patterns, or prepare a reviewable evidence PR without model-backed GitHub…
Compliance Checker
Check regulatory compliance across finance, tax, employment, data privacy, and industry-specific requirements.
traceability-gate
Enforces parent-link lineage across requirement layers.
wendao
Internal guardian skill for creating and editing Wendao DocOS documentation.
Advisory Board Builder
Recruit, structure, and manage advisory boards for strategic guidance.
Board Meeting Prep
Prepare board meeting decks, updates, and materials for effective governance.