tidy

tidy is a skill for Claude Code from jason-c-dev/obsidian-mcp. It costs 28 tokens per session (438 once invoked), scanned A, original, MIT.

A note-cleaning tool that turns rough or voice-transcribed notes into organized notes with headings, tasks, tags, dates, and links to related notes.

In plain words
What is it for?
Use it to clean an individual note, extract action items, connect related notes, and preserve important decisions or warnings in an Obsidian vault.
Why use it?
It removes filler and transcription mistakes and saves you from organizing notes by hand. It also makes decisions, questions, and follow-up work easier to find.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to clean an individual note, extract action items, connect related notes, and preserve important decisions or warnings in an Obsidian vault.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jason-c-dev/obsidian-mcp/tidy
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 jason-c-dev/obsidian-mcp --skill tidy
Clone the repo
git clone --depth 1 https://github.com/jason-c-dev/obsidian-mcp

Made for: Claude Code.

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.

agentmods badge for tidy

README.md
[![agentmods](https://agentmods.dev/badge/skills/jason-c-dev/obsidian-mcp/tidy.svg)](https://agentmods.dev/skills/jason-c-dev/obsidian-mcp/tidy)
Your own site
<a href="https://agentmods.dev/skills/jason-c-dev/obsidian-mcp/tidy"><img src="https://agentmods.dev/badge/skills/jason-c-dev/obsidian-mcp/tidy.svg" alt="Measured on agentmods" 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 438 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00438
Opus 5 $0.00014 $0.00219
Sonnet 5 $0.00006 $0.00088
Haiku 4.5 $0.00003 $0.00044

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

Security

Grade A, and why

tidy 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 7d 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.

skills/tidy/SKILL.md · 47 lines

What it actually says

Tidy Note

Take a raw/unstructured note (often from voice transcription) and restructure it.

Steps

  1. Read the note — call vault_read with file: "$ARGUMENTS"

  2. Analyze the content — identify:

    • Key topics and themes
    • Action items and tasks
    • References to people, projects, or other notes
    • Decisions made
    • Questions or open items
  3. Read related notes to understand context — call vault_search with relevant keywords from the note

  4. Restructure the note with:

    • YAML frontmatter (tags, date, related project)
    • Clear headings for each topic/section
    • Action items as - [ ] task format
    • [[Wikilinks]] to related notes
    • Callouts for important decisions or warnings (> [!tip], > [!warning])
    • Remove filler words and transcription artifacts ("um", "uh", "okay so")
  5. Overwrite the note — call vault_create with name: "$ARGUMENTS", overwrite: true, and the cleaned content

  6. Report what changed — summarize what was extracted and restructured.

Vault Conventions

  • Always include YAML frontmatter with at least tags and date
  • Use [[wikilinks]] to connect related notes
  • Use - [ ] for actionable items
  • Use Obsidian callouts: > [!note], > [!tip], > [!warning]

Guidelines

  • Preserve all meaningful information — don't drop content, just restructure
  • Extract every action item as a task
  • Be aggressive about removing transcription noise but conservative about removing meaning
  • If it's a meeting transcript, identify speakers if possible and format as a meeting note
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.

  1. 7d ago First seen · 47 lines · 28 tokens per session scan A e9149df2fcc2

Subscribe to this mod's changes

tidy is a skill published in the GitHub repository jason-c-dev/obsidian-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 438 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-31.