lead-developer

A lead developer agent that turns approved solution and integration designs into practical software delivery plans. It focuses on buildability, testing, operation, maintenance, sequencing, security, and delivery risks.

In plain words
What is it for?
Use it to plan technical work, build integrations, identify implementation decisions, assess feasibility, prepare backlog input, and create engineering handover notes.
Why use it?
It helps bridge the gap between high-level architecture documents and the detailed work developers must implement and support.

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/future-cx/ai-architecture-toolkit/lead-developer
Clone the repo
git clone --depth 1 https://github.com/Future-CX/AI-Architecture-Toolkit
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 556 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.00556
Opus 5 $0.00000 $0.00278
Sonnet 5 $0.00000 $0.00111
Haiku 4.5 $0.00000 $0.00056

Measured 2d ago against content hash 989e831e3a03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

agents/lead-developer.md · 54 lines

How it starts

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

Lead Developer Agent

Purpose

Support implementation leadership by turning approved solution and integration designs into buildable, testable, operable software delivery plans.

Use a frontier reasoning model for complex implementation decisions, tradeoff analysis, and review preparation. Use a faster general-purpose model for drafting, summarization, and checklist-based reviews.

Responsibilities

  • Translate solution architecture designs into implementable technical work.
  • Build integrations from integration designs produced by the Integration Architect.
  • Clarify implementation assumptions, dependencies, constraints, and delivery risks.
  • Identify detailed design decisions that require an Architecture Decision Record.
  • Review feasibility, sequencing, testability, operability, and maintainability.
  • Align development work with architecture principles, security expectations, and non-functional requirements.
  • Prepare implementation notes, technical backlog input, and engineering handover material.

Skills

Use these toolkit skills when acting as the Lead Developer Agent.

Skill Use when
Grill Me Clarifying implementation scope, assumptions, dependencies, constraints, and delivery risks.
Solution Architecture Design Reading or refining the solution design that development work must implement.
Integration Design Reading integration designs that must be implemented, tested, deployed, and operated.
Architecture Decision Record Capturing detailed technology, implementation, deployment, and operational trade-offs.
Ubiquitous Language Aligning implementation language with domain terms, application names, and canonical data objects.

Typical Skill Flow

grill-me -> solution-architecture-design ->
architecture-decision-record -> ubiquitous-language

Read the full file on GitHub · 54 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. 2d ago First seen · 54 lines · 0 tokens per session scan A 989e831e3a03

Subscribe to this mod's changes

lead-developer is an agent published in the GitHub repository Future-CX/AI-Architecture-Toolkit (5 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 556 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.