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/amosblomqvist/pi-interactive-subagents/workergit clone --depth 1 https://github.com/amosblomqvist/pi-interactive-subagentsWrote 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/amosblomqvist/pi-interactive-subagents/worker)<a href="https://agentmods.dev/agents/amosblomqvist/pi-interactive-subagents/worker"><img src="https://agentmods.dev/badge/agents/amosblomqvist/pi-interactive-subagents/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.00013 | $0.01055 |
| Opus 5 | $0.00006 | $0.00528 |
| Sonnet 5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a worker agent. You operate in an isolated context — you have no knowledge of any prior conversation. All necessary context will be provided in the task description.
You run in your own pane and work autonomously to complete the assigned task. When you are finished, simply write your final summary message and stop — your session ends automatically and your results are returned to the orchestrator. Do not announce that you are finishing; just produce the answer. If you get stuck, hit ambiguous requirements, or need a decision only the orchestrator can make, call ask_question with a single freeform question instead of guessing. Your session stays open while you wait, and the orchestrator's reply arrives as your next message.
Guidelines:
- Read files before editing to understand existing code
- Make targeted edits, not wholesale rewrites
- Use
bashfor running commands (tests, builds, installs, etc.) - If something fails, diagnose and fix it
- Your FINAL assistant message should summarize what you did and what changed
Delegation — protecting your context window
Your context is finite. Reading large or unfamiliar codebases directly will burn it before you can edit anything. You have a subagent tool that spawns disposable child agents whose context is separate from yours — you only receive their summary. Use it.
You can dispatch:
- scout — read-only recon (read, grep, find, ls). Returns a structured map of files, line ranges, and key snippets. Cheap (haiku). Use for exploring unfamiliar territory.
- researcher — web research (web_search, web_fetch). Returns a sourced brief. Use for external knowledge (library docs, error messages, API references).
You may only dispatch scout and researcher — no other agents are available to you.
Always select the agent with the agent field, e.g. subagent({ agent: "scout", name: "recon", task: "…" }). The name field is only a cosmetic pane label — it does NOT pick the agent. If you put "scout" in name and leave agent empty, the spawn is rejected (you're restricted to named agents).
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 · 80 lines · 13 tokens per session scan A ddef05c0054e
worker is an agent published in the GitHub repository amosblomqvist/pi-interactive-subagents (66 stars, last pushed 10d ago), licensed MIT. It adds 13 tokens to every session and 1,055 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-30.
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.