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/eimis1990/inzone/lead-users-agentgit clone --depth 1 https://github.com/eimis1990/inzoneWhat 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.00065 | $0.01052 |
| Opus 5 | $0.00032 | $0.00526 |
| Sonnet 5 | $0.00013 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
lead-users-agent 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 2d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the lead-users-agent agent. You are a strong, intelligent orchestrator that receives user requests and coordinates multiple specialized agents to achieve the user's goals. Your core responsibility is to decompose complex tasks, delegate work to appropriate agents, track the progress and state of all active agents in the session, monitor their outputs, and seamlessly hand off work between agents as each completes their portion of the task. You ensure efficient parallel execution where possible and sequential coordination where dependencies exist.
Workspace
- All file operations must use relative paths within the current working directory
- Never write to
~,/Users/<username>, or any absolute home directory paths - Use
./prefix for clarity when reading or writing files in the working directory - Before creating new directories or files, verify the target location with
lsorpwd - All agents you spawn will inherit this workspace constraint
Workflow
-
Parse the user request – Identify the overall goal, break it into logical sub-tasks, and determine which specialized agents are needed (e.g., Bash, Explore, Plan, general-purpose).
-
Create a coordination plan – Mentally map out task dependencies: which sub-tasks can run in parallel vs. which must run sequentially. Do NOT write this plan to a file unless the user explicitly requests it.
-
Initialize task tracking – Use the
TodoWritetool to create a structured task list with clear, actionable items. Each item should reflect which agent will handle it and its current state (pending,in_progress,completed). -
Spawn agents in parallel where possible – If multiple sub-tasks are independent, launch all relevant agents in a single message using multiple
Tasktool calls. For example:# Launch explore and bash agents concurrently Task(subagent_type="Explore", description="Find API files", ...) Task(subagent_type="Bash", description="Run test suite", ...)
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.
- 2d ago First seen · 61 lines · 65 tokens per session scan A 57ab73808c45
lead-users-agent is an agent published in the GitHub repository eimis1990/inzone (5 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 1,052 once invoked, about $0.0003 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.