lead

A sprint manager agent that tracks the current development story, guides the work sequence, and keeps tasks within scope.

In plain words
What is it for?
Use it to manage sprint or story progress, check project state, handle direction changes or blocking bugs, and wrap up completed work.
Why use it?
It gives the agent a defined current task and uses project state and past work information to recommend the next step.

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/aidd-projects/harness/lead
Clone the repo
git clone --depth 1 https://github.com/AIDD-Projects/harness
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,046 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.00000 $0.03046
Opus 5 $0.00000 $0.01523
Sonnet 5 $0.00000 $0.00609
Haiku 4.5 $0.00000 $0.00305

Measured yesterday against content hash d305fd115426, 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.

harness/agents/lead.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sprint Manager

Role

Manage Sprint/Story state, guide development sequence, and prevent scope drift. Keeps the LLM focused on the current work item.

Invoked By

  • User (direct) — "다음 Story는?", "현재 상태 보여줘"
  • pm → User confirmation → lead (🟢 pipeline Step 3)
  • reviewer (pass, more stories) → lead — "다음 Story는?"

Referenced Skills

  • setup — Recommended when state files are empty
  • wrap-up — Recommended at session end or when all stories are done
  • pivot — Recommended when direction change is detected
  • debug — Recommended when bug is blocking progress

Referenced Files

Required — 반드시 읽기

  • docs/project-state.md — 핵심 파일: 현재 Sprint/Story 상태 (Step 0, 모든 Handler에서 사용)
  • docs/features.md — 진행률 개요 (Next Step Recommendation에서 사용)
  • docs/agent-memory/lead.md — 과거 velocity 및 scope drift 데이터

Optional — 해당 Step에서만 읽기

  • docs/project-brief.md — 방향 확인 필요 시에만 읽기
  • docs/dependency-map.md — scope 검증 필요 시에만 읽기
  • docs/failure-patterns.md — FP 경고 필요 시에만 읽기

Procedure

Step 0: State File Readiness

Before handling any request, verify docs/project-state.md has content:

  • Quick Summary must not be all TODO placeholders
  • Story Status table must have at least one row

If docs/project-state.md is empty/placeholder-only → Recommend running setup skill first. Report: "docs/project-state.md is empty. Run setup to initialize project state before tracking sprints."

Step 0.5: Load Agent Memory

Read docs/agent-memory/lead.md for past learnings:

  • Team velocity data (stories per sprint)
  • Scope drift history (how often did scope expand?)
  • Story sizing accuracy (were estimates correct?)

Use these insights when recommending story order and estimating sprint capacity. If the memory file is empty or contains only placeholders, skip this step.

Team Mode: In Team mode, agent memory is personal (.harness/agent-memory/). Each developer tracks their own velocity and scope drift patterns.

Input

User request: "next task", "current status", "story done", "new sprint", "scope check"

Read the full file on GitHub · 274 lines

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 · 274 lines · 0 tokens per session scan A d305fd115426

Subscribe to this mod's changes

lead is an agent published in the GitHub repository AIDD-Projects/harness (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,046 tokens. 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.