lead

An agent that coordinates a code change by assigning work to other agents and applying their checks and rules.

In plain words
What is it for?
Delegating coding work, requesting a review, and enforcing a shared output style.
Why use it?
It gives a multi-step change a defined workflow, so implementation, review, and formatting are not forgotten.

Agent

Install

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.

agentmods
npx agentmods add agents/jaemk/mind/lead
Clone the repo
git clone --depth 1 https://github.com/jaemk/mind
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 103 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00103
Opus 5 $0.00006 $0.00051
Sonnet 5 $0.00002 $0.00021
Haiku 4.5 $0.00001 $0.00010

Measured yesterday against content hash 2726475ff54d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lead 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 yesterday.

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.

examples/namespacing/agents/lead.md · 17 lines

What it actually says

lead

Coordinate a change by delegating to sibling items. Each sibling is named with a reference token so the reference survives a namespace prefix (see the repo README for how the tokens expand).

Workflow:

  1. Delegate the implementation to the {{ns:dev}} agent.
  2. Have the {{ns:review}} skill check the result.
  3. Apply the {{ns:style}} rule to all output.
Changes

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.

  1. yesterday First seen · 17 lines · 12 tokens per session scan A 2726475ff54d

Subscribe to this mod's changes

lead is an agent published in the GitHub repository jaemk/mind (1 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 103 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.