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/urmzd/dotfilesWrote 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/urmzd/dotfiles/curator)<a href="https://agentmods.dev/agents/urmzd/dotfiles/curator"><img src="https://agentmods.dev/badge/agents/urmzd/dotfiles/curator/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/urmzd/dotfiles/curator"><img src="https://agentmods.dev/badge/agents/urmzd/dotfiles/curator.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.00664 |
| Opus 5.5 | $0.00007 | $0.00266 |
| Sonnet 5.5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 65 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.shfor 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), orflagged (needs human call).
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 Changed · -9 lines · -106 tokens per session 97ce042ecfe8
- 1mo ago First seen · 74 lines · 124 tokens per session scan A 039257fdcd15
curator is an agent published in the GitHub repository urmzd/dotfiles (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 18 tokens to every session and 664 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-31.
Other agents, from other repositories
dspix
A narrowly scoped worker for a team of coding agents. It handles mechanical tasks such as searching, listing files, extracting fields, changing formats, checking repetition, making small edits, and running focused tests.
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.
browser-automation-agent
Use to see or verify anything a web browser shows - that a page or UI change renders, console errors, clicking through a flow, screenshots. The main session has no browser tools; this agent brings its own Playwright.
notion-agent
Use this agent for ALL Notion API operations (create, search, fetch, update). Never use Notion MCP tools directly. Triggers include notion, writing database, create page, search workspace, fetch page, update page, query database.
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.