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 alexeyshishin/as-skill --skill obsidian-note-criticgit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/obsidian-note-critic)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/obsidian-note-critic"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/obsidian-note-critic/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/alexeyshishin/as-skill/obsidian-note-critic"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/obsidian-note-critic.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.00121 | $0.01999 |
| Opus 5 | $0.00060 | $0.01000 |
| Sonnet 5 | $0.00024 | $0.00400 |
| Haiku 4.5 | $0.00012 | $0.00200 |
Grade A, and why
obsidian-note-critic 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 12d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The skill analyzes a note along four axes:
- Similar knowledge — what already exists in the base on this topic
- Opposing views — alternative approaches, competing ideas
- Contradictions — where the note diverges from existing knowledge
- Reasoned critique — weak points in logic, wording, coverage completeness
Vault root folder (<vault>/): set at install time (--vault or the OBSIDIAN_VAULT env var). See .claude/rules/vault-struct.md.
Output language: Russian, technical terms in English.
Algorithm
1. Read the note
Read the full content. Note down for yourself:
- Main thesis — what's being claimed or described (one phrase)
- Key claims — 3–7 specific statements from the text
- Domain — field of knowledge (SRE, DevOps, career, management, etc.)
- Sources — is there a
sourcesfield,links, quotes, or is this purely personal opinion - Confidence — the
confidencefield, if present
2. Search for similar topics
Use mcp__obsidian-hybrid-search__myvault_search with several phrasings to catch different angles on the same topic. Good practice is to give three queries: one in Russian, one in English, and one "by contrast" (what this is NOT, or how it differs).
Parameters:
queries: [main thesis, key concept, English equivalent]limit: 8threshold: 0.3rerank: true
Skip the note being analyzed itself (usually rank 1). Collect the 4–7 most relevant results.
3. Search for opposing views
Formulate queries that catch alternative approaches or criticism:
queries: ["alternative to [thesis]", "criticism of [approach]", "against [concept]", "downsides of [method]"]limit: 6threshold: 0.25
Also: if the note is about practice X — search for "when X doesn't work", "limitations of X", "X vs Y".
4. Contradiction analysis
Compare the note's content against the similar notes found. Look for:
- Direct contradictions — note A claims X, note B claims not-X
- Terminological mismatches — the same concept is called different things, causing confusion
- Contextual conflicts — a claim is true in one context, wrong in another
- Outdated knowledge — a later note updates or overrides this one
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.
- 12d ago First seen · 242 lines · 121 tokens per session scan A 2234e15ec4f4
obsidian-note-critic is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 24d ago), licensed MIT. It adds 121 tokens to every session and 1,999 once invoked, about $0.0006 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
obsidian
Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.4.1, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use…
loop-engineering
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
harness-engineering
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.
agent-teams-command
Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
agentic-engineering
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
anthropic-os
Use when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error learning.