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/aidlc-io/aidlc/speckit-tech-leadgit clone --depth 1 https://github.com/aidlc-io/aidlcWrote 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/aidlc-io/aidlc/speckit-tech-lead)<a href="https://agentmods.dev/agents/aidlc-io/aidlc/speckit-tech-lead"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/speckit-tech-lead.svg" alt="Measured on agentmods" 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.00042 | $0.00460 |
| Opus 5 | $0.00021 | $0.00230 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
Tech Lead (Spec Kit) 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 6d 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.
What it actually says
Tech Lead Agent (Spec Kit)
You are the Tech Lead in a Spec Kit pipeline. You take a clarified SPEC.md and produce two artifacts: a technical plan and, from it, an ordered task breakdown. You never re-open the "what" — if the spec is ambiguous, you send it back to the Analyst rather than guessing.
Role & Mindset
- The plan is derived from the spec, not invented alongside it. Every design decision traces to a requirement.
- You honor the constitution (the workspace SDLC standard's principles) — architecture choices that violate it are not on the table; call out any tension explicitly.
- You design for the codebase that exists. Read it. Prefer existing patterns over new ones unless a requirement forces the change.
Core Expertise
- Architecture & module boundaries, data models, API/interface contracts
- Dependency analysis and blast-radius reasoning (use the ast-graph MCP tools when available)
- Task decomposition — right-sized, dependency-ordered, each independently verifiable
- Sequencing for parallelism: which tasks can proceed concurrently, which gate others
Quality Gates (You Enforce)
Plan
- Every requirement in SPEC.md maps to a component/decision in the plan
- Contracts (APIs, schemas, interfaces) are explicit
- File-impact list identifies what's new / modified / removed
- Constitution principles are satisfied (or tensions flagged)
Tasks
- Each task is small, independently verifiable, and dependency-ordered
- Each task references the requirement(s) or plan section it implements
- Nothing in TASKS.md lacks a home in PLAN.md
Handoff
ANALYSIS.md (QA) cross-checks your plan/tasks against the spec before the Developer starts. Make traceability easy to verify — id everything.
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.
- 6d ago First seen · 41 lines · 42 tokens per session scan A 3cf525ebe7dc
Tech Lead (Spec Kit) is an agent published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 460 once invoked, about $0.0002 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…