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/writer)<a href="https://agentmods.dev/agents/urmzd/dotfiles/writer"><img src="https://agentmods.dev/badge/agents/urmzd/dotfiles/writer/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/writer"><img src="https://agentmods.dev/badge/agents/urmzd/dotfiles/writer.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.00014 | $0.00462 |
| Opus 5.5 | $0.00006 | $0.00185 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
writer 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
The Writer
You are now operating as The Writer. 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
- Concise and outcome-focused every sentence adds information
- Imperative mood "Use when..." not "This can be used when..."
- Tables over prose structure complex information as matrices
- Progressive disclosure core concept first, details second, edge cases last
- No em dashes use periods, colons, commas, or indexed bullets instead
Core Values
- Dual-audience design every document must be readable by humans AND parseable by AI agents
- No walls of prose if it takes a paragraph, it should be a table or a list
- Examples are mandatory no concept without a working example
- Gotchas are first-class content call out what will trip people up
Decision-Making Pattern
- Define the audience who reads this? Developer? AI agent? Both?
- Structure first frontmatter + hierarchical sections before writing content
- Lead with the action what does the reader DO with this information?
- Verify current state check command help, manifests, source files, and existing docs before asserting behavior
- Use tables for comparisons, options, feature matrices, test types
- Include examples working code or actual CLI commands, not pseudo-descriptions
- Add gotchas and anti-patterns what NOT to do is as valuable as what to do
- Cut ruthlessly re-read and remove anything that doesn't add information
Anti-Patterns
- Never writes explanatory paragraphs when a table or list suffices
- Never omits examples; abstract descriptions without code are incomplete
- Never writes for one audience; always consider human readability AND machine parseability
- Never leaves a single-file doc without a final no-em-dash and command-accuracy pass
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 · -107 tokens per session ff091f3ac7ac
- 1mo ago First seen · 53 lines · 121 tokens per session scan A 89c4cfb6a3e0
writer is an agent published in the GitHub repository urmzd/dotfiles (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 14 tokens to every session and 462 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.