om-humanize

om-humanize is a command for Claude Code from breferrari/obsidian-mind. It costs 23 tokens per session (849 once invoked), scanned A, original, MIT.

A command for editing a note so its wording matches the user's established writing style. It reads selected writing samples, identifies recurring style choices, and edits the target note in place.

In plain words
What is it for?
Use it on notes in the knowledge vault, such as personal writing, one-to-one notes, performance reviews, incident records, or brain-dump pages.
Why use it?
It helps make drafted text sound consistent with the user's real writing instead of using a generic assistant style. It also adapts the tone to the note's location and context.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the obsidian plugin — 8 skills, 20 commands, 10 agents, 5 hooks, 1 MCP server shipped together

About the project

Obsidian Mind is an Obsidian vault that stores notes, links, indexes, and other accumulated context so AI coding agents can retain memory across sessions. It is designed for Claude Code and also supports Codex CLI and Gemini CLI through shared hooks, commands, and vault data. Its catalogue add-ons package the vault’s commands, agents, skills, hooks, instructions, settings, plugin, and MCP integration.

breferrari/obsidian-mind · 4,599 stars · on GitHub

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.

agentmods
npx agentmods add commands/breferrari/obsidian-mind/om-humanize
Clone the repo
git clone --depth 1 https://github.com/breferrari/obsidian-mind

Made for: Claude Code.

Or install obsidian, the plugin that ships this one along with the rest of its 8 skills, 20 commands, 10 agents, 5 hooks, 1 MCP server.

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 om-humanize

README.md
[![agentmods](https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-humanize.svg)](https://agentmods.dev/commands/breferrari/obsidian-mind/om-humanize)
Your own site
<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-humanize"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-humanize.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00023 $0.00849
Opus 5 $0.00012 $0.00425
Sonnet 5 $0.00005 $0.00170
Haiku 4.5 $0.00002 $0.00085

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

Security

Grade A, and why

om-humanize 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 6d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • humanize — 95% identical, 14 lines differ
.claude/commands/om-humanize.md · 83 lines

How it starts

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

Edit a note to match your writing voice. This is voice calibration, not pattern removal — learn HOW you write, not just what to avoid.

Usage

/om-humanize <file path or note name>

Workflow

1. Load Voice Samples

Read 2-3 recent notes you actually wrote or heavily edited to calibrate voice:

  • brain/North Star.md — how you write about yourself
  • The most recent work/1-1/*.md note — natural conversational voice
  • Any brain note with your authentic writing style

Extract voice fingerprint: sentence length, punctuation habits, how you open sections, how you qualify statements, ratio of direct-to-hedged language, use of dashes and fragments.

2. Read Target Note

Read the note specified in $ARGUMENTS (resolve as wikilink name or file path).

Detect context from frontmatter and folder:

  • work/1-1/ → conversational, direct, uses "I", okay to be informal
  • perf/ review content → corporate-confident but human, evidence-based, respect charcount
  • work/incidents/ → precise, factual, timeline-oriented, no filler
  • brain/ → terse shorthand, fragments okay
  • Default → colleague-to-colleague, like explaining something in a 1:1

3. Edit In-Place

Rewrite the note's content to match your voice. Key principles:

Voice rules (from samples):

  • Direct statements, not hedged ones ("This was stressful" not "This presented some challenges")
  • Match your natural rhythm — fragments, dashes, whatever you actually use
  • Observations should be sharp, not softened
  • A concise 600-char section is better than a padded 950-char one

Anti-patterns (kill these):

  • "Notably", "significantly", "demonstrates", "leveraged", "facilitated"
  • "It's worth noting that..." — just note it
  • "This showcases..." — just describe what happened
  • Hedge stacking: "potentially", "arguably", "it could be said that"
  • Empty transitions: "Moving forward", "In terms of", "With regard to"
  • Passive voice where active is natural: "was identified" → "found"
  • Bullet points that all start with the same word pattern
  • Rhetorical questions followed by immediate answers

Read the full file on GitHub · 83 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.

  1. 6d ago First seen · 83 lines · 23 tokens per session scan A bc800052b91c

Subscribe to this mod's changes

om-humanize is a command published in the GitHub repository breferrari/obsidian-mind (4,599 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 849 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.