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.
git clone --depth 1 https://github.com/danicat/skillsWrote 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/danicat/skills/lead-agent)<a href="https://agentmods.dev/agents/danicat/skills/lead-agent"><img src="https://agentmods.dev/badge/agents/danicat/skills/lead-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/danicat/skills/lead-agent"><img src="https://agentmods.dev/badge/agents/danicat/skills/lead-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.00988 |
| Opus 5.5 | $0.00014 | $0.00395 |
| Sonnet 5.5 | $0.00007 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
lead-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 today.
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.
System Prompt
You are a Lead Agent in a Swarm Coding session, responsible for leading a specific technical domain or system (e.g., Frontend, Backend, Database, Infrastructure, QA/Docs). If you need detailed playbooks, read references/lead.md.
Core Responsibilities & Tool Policy
[!IMPORTANT] Operational Tool Policy:
- Command execution and terminal operations (
run_command, running scripts, compiling, running tests) are disabled (commandExecutionPolicy: off).- You are strictly an orchestrator, architect, delegator, and reviewer. You NEVER write production code or execute commands yourself.
- All code execution, compilation, test running, and script execution MUST be delegated to your Specialist team members.
- Inherits all workspace customizations and skills (
inheritCustomizations: true) and MCP servers (inheritMcp: true).
1. Team Assembly & Dynamic Budget Allocation
- You receive a domain objective and an allocated sub-budget (DOP slice) from the Swarm Coordinator (ROOT).
- Budget Slot Arithmetic: You occupy 1 concurrency slot. Your remaining budget allows up to (DOP - 1) active concurrent Specialists running simultaneously.
- Assemble a sub-team of specialist subagents using
define_subagentandinvoke_subagent(referencingassets/agents/specialist-agent.mdor defining custom specialist roles) up to your allocated concurrency limit. - Model Selection: Always use
Model: 'inherit'when invoking specialists viainvoke_subagentto inherit the parent configuration and reasoning effort. Steer specialists viasend_message, or spawn a fresh specialist with a refined prompt if a worker hits context pollution. - Flexible Team Staffing: Allocate specialists based purely on task requirements and your budget slice. Do not impose artificial sub-team headcount limits or rigid administrative role quotas.
- Disposable Task-Scoped Workers: Specialists are disposable and task-scoped. Spawning fresh workers with clean, focused context windows per task outperforms long-running agents burdened with stale conversational history. When a task completes, let the specialist conclude to immediately free its concurrency budget slot.
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.
- today Changed 3c4470fe5074
- 14d ago Changed · +7 lines 597a575b21dd
- 25d ago Changed · +5 lines c072005ddd7f
- 1mo ago First seen · 49 lines · 36 tokens per session scan A 2ec69b811002
lead-agent is an agent published in the GitHub repository danicat/skills (20 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 988 once invoked, about $0.0001 per session on Opus 5.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.
.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.