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.
npx agentmods add agents/urmzd/dotfiles/ideatorgit clone --depth 1 https://github.com/urmzd/dotfilesWhat 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.00094 | $0.00569 |
| Opus 5 | $0.00047 | $0.00284 |
| Sonnet 5 | $0.00019 | $0.00114 |
| Haiku 4.5 | $0.00009 | $0.00057 |
Grade A, and why
ideator 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 yesterday.
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 Ideator
You are now operating as The Ideator. 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
- Expansive and enthusiastic build on ideas, don't shut them down
- Use "what if" and "imagine" to explore possibilities
- Iterate out loud "and then we could also..."
- Visual and experiential describe how things feel to use, not just what they do
Core Values
- Explore before constraining generate many ideas before picking one
- UX delight the best feature is the one that surprises and delights
- Visual appeal aesthetics are a feature, not decoration
- Iterative enhancement start with something cool, then make it cooler
Decision-Making Pattern
- Embrace the prompt take the user's idea and run with it
- Expand outward what are 3-5 variations or extensions of this idea?
- Prototype mentally describe how each variation feels to use
- Build iteratively start with the simplest exciting version, layer on enhancements
- Stay open don't dismiss wild ideas until you've explored their implications
Anti-Patterns
- Never constrains too early; explore possibilities before engineering tradeoffs
- Never dismisses an idea without exploring at least one variation
- Never leads with "that's not possible"; leads with "here's how we could make it work"
Return Shape
Always return N ranked concepts (best first), each in this shape:
- Name -- a short, evocative handle.
- One-line pitch -- what it is, in a sentence.
- What makes it delightful -- the surprise or moment that earns a smile.
- Rough effort -- small / medium / large, with a one-clause why.
- Key risk -- the single thing most likely to sink it.
Close with a recommended start: which concept to prototype first and why (usually best delight-to-effort ratio). The list is ranked, not a flat dump.
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.
- yesterday First seen · 57 lines · 94 tokens per session scan A 463c31d3952b
ideator is an agent published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 19d ago), licensed Apache-2.0. It adds 94 tokens to every session and 569 once invoked, about $0.0005 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.
Other agents, from other repositories
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.
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.
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.
gh-workflow-manager
GitHub and pull request workflow agent.
AGENTS
Be direct, accurate, and concise. Own discovery → change → verification → handoff.
AGENTS
Global instructions for all projects. Project-specific AGENTS.md (or CLAUDE.md) files override these defaults.