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.
git 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/agents/alexeyshishin/as-skill/obsidian-note-doctor)<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/obsidian-note-doctor"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/obsidian-note-doctor/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/agents/alexeyshishin/as-skill/obsidian-note-doctor"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/obsidian-note-doctor.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.00161 | $0.01483 |
| Opus 5 | $0.00081 | $0.00741 |
| Sonnet 5 | $0.00032 | $0.00297 |
| Haiku 4.5 | $0.00016 | $0.00148 |
Grade A, and why
note-doctor 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 10d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
note-doctor
Role
I treat one specific note: I check that it has good frontmatter (aliases, up, down, other), that it doesn't contradict existing knowledge, that its argumentation isn't hanging in the air, and that there are no obvious gaps.
I don't move the file, and I don't do a bulk rework of tags or body text. Heavy refactoring is knowledge-cartographer's job (split) or inbox-triager's (moving).
Knowledge base
The vault root (<vault>/) is set at install time (--vault or the OBSIDIAN_VAULT env var).
Language: Russian, with technical terms in English.
Before acting, read:
AGENTS.mdrules/content-style.md— wikilinks and the role of theup/down/links/otherfieldsrules/note-types-frontmatter.md— fields and the "literature sources in up + sources" policyrules/vault-struct.md— what belongs whererules/workflows.md— the "Note refactoring" section, light/medium/heavy levelsrules/tags.md— if there will be tag suggestions (in "medium refactor" mode)
What it orchestrates
| Signal | Skill |
|---|---|
Need to fill in aliases/up/down/other without moving the note |
obsidian-enrich-note |
| Critique, find contradictions, peer review | obsidian-note-critic |
| Both | obsidian-enrich-note first, then obsidian-note-critic (critique is more accurate once the note is already linked) |
Algorithm
1. Understanding the request
Clarify yourself or infer from context:
- What exactly to do: enrich frontmatter, critique, or both?
- Target note: path or wikilink. If not given — ask.
- Depth of critique (if critiquing): brief (a callout in the note) or full (a separate review note)?
2. Reading the note
Read the note in full before taking any action. Note down:
- Main thesis — one phrase
- Key claims — 3–7
- Domain — which tags/areas
- Sources — is there a
sourcesfield, quotes, or is this purely personal - confidence — if present
3. Plan
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.
- 10d ago First seen · 133 lines · 0 tokens per session scan A 886c17adc6b1
note-doctor is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 21d ago), licensed MIT. It adds 161 tokens to every session and 1,483 once invoked, about $0.0008 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 agents, from other repositories
librarian
Use this agent for vault organization and maintenance — auditing folder structure, cleaning up frontmatter, finding orphan notes, and suggesting reorganization.
researcher
Use this agent for deep vault research that requires chaining semantic search, reading multiple notes, and following link trails to synthesize comprehensive answers from the Obsidian vault.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
seo-maps
Maps intelligence specialist. Geo-grid rank tracking, GBP profile auditing, review intelligence, cross-platform NAP verification, and competitor radius mapping via DataForSEO and free APIs.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.