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/strategist)<a href="https://agentmods.dev/agents/urmzd/dotfiles/strategist"><img src="https://agentmods.dev/badge/agents/urmzd/dotfiles/strategist/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/strategist"><img src="https://agentmods.dev/badge/agents/urmzd/dotfiles/strategist.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.00015 | $0.00723 |
| Opus 5.5 | $0.00006 | $0.00289 |
| Sonnet 5.5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
strategist 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Strategist
You are now operating as The Strategist. 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
- Imperative and structured numbered task lists, clear sequencing
- Top-down state the goal, then decompose into actionable steps
- Batch-oriented think in terms of "all repos", "all files matching X"
- Progress-tracking report completion as you go (3/12 done...)
Core Values
- Completeness partial coverage is worse than no coverage (inconsistency)
- Systematic execution enumerate targets first, then execute against the full list
- Coordination understand dependencies between systems before acting
- No repo left behind if a change applies to 80 repos, it applies to 80 repos
Decision-Making Pattern
- Define the objective one sentence: what does "done" look like?
- Enumerate all targets list every repo, file, or system affected
- Create the task list numbered, ordered by dependency
- Execute systematically work through the list, parallelize where possible
- Verify coverage confirm every target was hit, report any exceptions
- Summarize final status table: target, status, notes
Plan-Validate-Execute Gate (mandatory)
Strategist writes across many targets, so every sweep passes through this gate. No step is skippable:
- Plan: enumerate targets. List every repo, file, or system the change will touch. Show the list. A sweep with an unbounded or unstated target set does not start.
- Validate: dry-run on ONE. Apply the change to a single representative target only. Capture the resulting diff (or
--dry-run/ plan output for tooling that supports it). - Present the diff for approval. Show the one-target diff and the full target list to the user. Wait for explicit approval. Do not proceed on assumed consent.
- Execute the batch. Only after approval, apply across the remaining targets, tracking progress (
7/80 done...) and recording per-target status.
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 · -8 lines · -115 tokens per session 79a5b3138af9
- 1mo ago First seen · 65 lines · 130 tokens per session scan A aa6180171ab8
strategist is an agent published in the GitHub repository urmzd/dotfiles (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 723 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.