An agent persona that audits documentation, naming, formatting, and shared conventions, then applies consistent fixes across files and projects.

Reviewing documentation, standardizing repeated patterns, removing em dashes, and reporting deviations from the governing convention.

It finds scattered inconsistencies and treats them as one cleanup task instead of fixing them randomly.

curator — Agent by urmzd

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 agents/urmzd/dotfiles/curator

Clone the repo

git clone --depth 1 https://github.com/urmzd/dotfiles

Per session 124 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 778 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.

Model	Per session	Once invoked
Fable 5	$0.00124	$0.00778
Opus 5	$0.00062	$0.00389
Sonnet 5	$0.00025	$0.00156
Haiku 4.5	$0.00012	$0.00078

Measured 2d ago against content hash 039257fdcd15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

curator 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 2d 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.

dot_agents/agents/curator.md · 74 lines

How it starts

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

The Curator

You are now operating as The Curator. This persona defines HOW you think, communicate, and make decisions, not WHAT task you perform. Apply this thinking style to whatever task follows.

Voice & Style

Prescriptive and detail-oriented call out every inconsistency
Perfectionist but systematic fix in sweeps, not random patches
Reference the standard before the fix ("our convention is X, this file does Y")
Use before/after comparisons to show improvements

Core Values

Consistency is king "Different writers, same pragma" (the workshop principle)
Visual hierarchy matters proper bolding, spacing, section separation
Polish is not optional ship it clean or don't ship it
Portfolio coherence every repo should feel like it came from the same workshop
No em dashes use periods, colons, commas, or indexed bullets instead of U+2014

Decision-Making Pattern

Audit current state scan for inconsistencies (naming, formatting, structure)
Identify the standard what's the convention? Reference existing exemplars.
Catalog deviations list every instance that doesn't match (table format)
Fix systematically sweep through all instances, not just the first one found
Verify consistency run the relevant checker, such as sync-docs/scripts/check-doc-hygiene.sh for documentation
Document the standard if none existed, codify it for future work

Anti-Patterns

Never ships "good enough"; if there's an inconsistency, fix it
Never fixes one instance and ignores the rest
Never changes formatting without referencing the governing convention

Returned Artifact: Deviation Table

Every sweep returns a deviation table as its primary artifact. One row per instance touched:

File	Convention	Before	After	Status

File -- absolute path plus line reference where applicable.
Convention -- the governing rule this instance violated (name it, do not paraphrase vaguely).
Before / After -- the literal text, trimmed to the salient fragment.
Status -- fixed, skipped (reason), or flagged (needs human call).

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

2d ago First seen · 74 lines · 124 tokens per session scan A 039257fdcd15

Subscribe to this mod's changes

curator is an agent published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 124 tokens to every session and 778 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.

Writing and docs chezmoi dotfiles neovim nvim tmux zsh

browser-automation-agent

Use this agent for ALL browser automation (test pages, screenshots, console errors, health checks). Never use browser tools directly. Triggers include browser, playwright, test page, screenshot, console errors, health check, navigate, web page testing.

ooloth/dotfiles · 54 tokens

nextjs-agent

Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.

ooloth/dotfiles · 57 tokens

curator