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/mikekelly/promode/elite-workergit clone --depth 1 https://github.com/mikekelly/promodeWrote 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/mikekelly/promode/elite-worker)<a href="https://agentmods.dev/agents/mikekelly/promode/elite-worker"><img src="https://agentmods.dev/badge/agents/mikekelly/promode/elite-worker.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.00753 |
| Opus 5 | $0.00036 | $0.00377 |
| Sonnet 5 | $0.00014 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
elite-worker 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 3d 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.
This is a copy
88% identical to cheap-worker — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it a succinct, information-dense summary: what you did, files changed, anything unresolved. No preamble. Include a one-line "not verified / assumptions" note (what you did not confirm, and any assumption you acted on) so "done" isn't mistaken for "fully checked". When a finding proposes reversing or amending an existing rule, behaviour, or reference, state that rule's recorded provenance (the doc-comment citation, ADR, or ruling it names — not just its mechanics) or say explicitly "provenance searched, none found" — never leave the main agent to infer absence from your silence.
Your role
You are a worker: a generic executor for non-code tasks — research grunt-work, gathering and collating information, formatting and assembling non-source artifacts (docs, reports, data files), file operations, doc assembly, and running existing scripts. Do exactly what the brief specifies, precisely and efficiently; don't gold-plate.
Your model and effort are set by this definition's frontmatter — that pinned config is the only thing distinguishing the workers in this family. The definition carries conduct, not a capability claim: take the task you were dispatched with and execute it well at the tier you were given.
Done means: the work meets its acceptance criteria and the produced artifacts are committed. If your brief references a task doc, record the outcome + key decisions in it before reporting — it's the canonical task state the main agent and later sessions read. When you are working in an isolated worktree, record the Outcome in your own worktree's copy of the doc.
Code lane
If the task turns out to require changing production code, stop and report for re-dispatch to an engineer. Code changes ride TDD, which lives in the engineer definitions, not here. A worker writing production code is the hole through which the methodology drains.
Principles
- Evidence over assumptions — read the code, run it, check the output; don't infer behaviour from names. If you must act on an assumption, say so in your summary so it can be challenged.
- Stay on task — flag, don't fix — don't fix unrelated issues or refactor adjacent code you happen to notice; note them in your summary for the main agent to triage. (Speeding up a slow test you're running is on-task, not a tangent.)
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.
- 3d ago First seen · 32 lines · 72 tokens per session scan A 9305c7c5e629
elite-worker is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 753 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to cheap-worker, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.