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/Michael-OvO/obsidian-knowledge-agentWrote 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/commands/michael-ovo/obsidian-knowledge-agent/polish)<a href="https://agentmods.dev/commands/michael-ovo/obsidian-knowledge-agent/polish"><img src="https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/polish/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/commands/michael-ovo/obsidian-knowledge-agent/polish"><img src="https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/polish.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.00018 | $0.00250 |
| Opus 5.5 | $0.00007 | $0.00100 |
| Sonnet 5.5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
polish 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 1mo 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.
What it actually says
Run the teaching-quality pass on the target ($ARGUMENTS, or the most recently changed
notes if none is given). Read .agents/style-guide.md first.
- Select the note(s). For a folder, polish the content and concept notes (skip indexes and source notes unless I ask).
- Review against the style guide: does the body read naturally top to bottom? Is the machinery off-stage (metadata in frontmatter, no rubric headings)? For technical notes, is it bullet-first with the artifacts that genuinely teach (runnable code, an equation, a diagram)? Are related links specific and useful?
- Rewrite only the failing parts — never restate a whole note and never change its meaning. Add a missing artifact only where it actually helps.
- Fix and wire wikilinks, then validate them (the bundled
scripts/validate_links.py, or the inline check in the workflow). Show me the diffs before committing.
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.
- 1mo ago First seen · 19 lines · 18 tokens per session scan A 1e65581a6ea2
polish is a command published in the GitHub repository Michael-OvO/obsidian-knowledge-agent (206 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 250 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
scope
Project-level scoping — refine a single living vault note for a project, with mandatory unknowns tracking. Re-entrant; agent-judged writes.
memory-update
Run the Memory Update protocol. Checks whether decisions, questions, assumptions, risks, tasks, or opportunities emerged in the current task and writes them to the right files, then prints the required end-of-task summary.
decompose
Feature/story breakdown — consume a ready-for-decompose scope doc and produce a task graph in the issue tracker. Re-entrant; tracker-as-canonical with vault breadcrumb.
sol
Run a one-shot task on the routed Codex model (gpt-5.6-sol by default) and relay its answer.
codex-usage
Show your ChatGPT/Codex weekly usage limits (via the local model-router proxy).
dossier
Force load of Dossier vault profile (and inbox check) before processing the rest of the user's request.