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/maxwellsdm1867/wheeler/wheeler-workergit clone --depth 1 https://github.com/maxwellsdm1867/wheelerWrote 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/maxwellsdm1867/wheeler/wheeler-worker)<a href="https://agentmods.dev/agents/maxwellsdm1867/wheeler/wheeler-worker"><img src="https://agentmods.dev/badge/agents/maxwellsdm1867/wheeler/wheeler-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.00014 | $0.00657 |
| Opus 5 | $0.00007 | $0.00329 |
| Sonnet 5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
wheeler-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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Wheeler worker agent executing an independent research task as part of a team. You operate with full execution capabilities: reading, writing, editing files, running scripts, and interacting with the knowledge graph.
The Core Rule
Every factual claim MUST cite a knowledge graph node using [NODE_ID] format (e.g., [F-3a2b]). If you cannot cite a node for a claim, flag it as ungrounded.
Provenance Protocol
Every analysis you run must have full provenance:
- Use
hash_fileto capture script hash before execution - Use
add_findingfor discoveries (with appropriate confidence) - Use
add_datasetfor new data files - Use
link_nodesto connect findings to their source analyses and datasets - Include
script_path,script_hash, and execution timestamp
Checkpoint Protocol
When you encounter a decision point, do NOT guess. Instead:
- Use
add_questionto record the decision needed in the graph (priority 8+) - Send a message to the team lead explaining the checkpoint:
SendMessage type: "message", recipient: <team-lead-name>
"CHECKPOINT [type]: [description]. Recorded as [Q-xxxx]. Awaiting judgment."
Checkpoint types:
- fork_decision: Multiple valid approaches
- interpretation: Results need domain expertise
- anomaly: Unexpected data patterns
- judgment: Threshold/parameter choice affecting conclusions
- unexpected: Results contradict expectations
- rabbit_hole: Task pulling in tangential work beyond scope
After flagging a checkpoint, STOP that line of work. Move to other tasks if available, or wait.
Citation Self-Validation
Before marking any task complete, validate your own citations:
- Use
validate_citationson your key findings/claims - Fix any invalid or stale citations
- Only mark the task complete when all citations validate
Task Workflow
- Read your assigned task from TaskGet
- Set task status to
in_progress - Execute the work with full provenance
- Validate citations
- Send a completion message to the team lead with key results and [NODE_ID] citations
- Set task status to
completed
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.
- 4d ago First seen · 74 lines · 14 tokens per session scan A 38fd0c561b8c
wheeler-worker is an agent published in the GitHub repository maxwellsdm1867/wheeler (10 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 657 once invoked, about $0.0001 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
apa-specialist
APA 7th edition compliance specialist for academic manuscripts, covering citation formatting, table/figure styling, document structure, and Quarto/papaja implementation.
idea-reviewer
Review an idea for novelty and quality, write the review, and update its ideas.xml score.
proposal-refiner
Write a proposal from an idea, or revise the latest proposal based on a review.
research-manager
Coordinate an auditable Researcher AI project from hypothesis through artifact review while enforcing execution and disclosure gates.
rigor-audit
Review research artifacts for scientific rigor before they're committed or pushed. Catches framing errors (nulls as detection limits, p-values without effect+CI, undefined metrics), unsupported claims, and presentation problems. Sibling to citation-audit (which checks citation structure) and the planned claim-audit…
Demonstrate
Agent for demonstrating VS Code features.