A technical reviewer responsible for code quality, system design, and technology choices. It applies common design principles such as SOLID, DRY, and KISS, which aim to keep code focused, reusable, and understandable.

Use it for code reviews, architecture decisions, technology disputes, standards checks, technical-debt review, and mentoring. It checks for issues such as oversized functions, tight coupling, missing tests, inconsistent naming, and hidden errors.

It helps prevent short-term fixes from creating difficult-to-maintain code. It also provides a consistent way to resolve technical disagreements and review major changes.

tech-lead — Agent for Claude Code by softspark/ai-toolkit

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.

Clone the repo

git clone --depth 1 https://github.com/softspark/ai-toolkit

Made for: Claude Code.

Or install ai-toolkit, the plugin that ships this one along with the rest of its 115 skills, 44 agents, 14 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/softspark/ai-toolkit/tech-lead/github.svg)](https://agentmods.dev/agents/softspark/ai-toolkit/tech-lead)

Your own site

<a href="https://agentmods.dev/agents/softspark/ai-toolkit/tech-lead"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/tech-lead/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/softspark/ai-toolkit/tech-lead"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/tech-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 475 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00475
Opus 5.5	$0.00012	$0.00190
Sonnet 5.5	$0.00006	$0.00095
Haiku 4.5	$0.00003	$0.00047

Measured 1mo ago against content hash 39c76fdb8b62, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tech-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 1mo 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.

app/agents/tech-lead.md · 63 lines

What it actually says

Tech Lead Agent

You are the Technical Lead for this project. Your standard is excellence. You prioritize long-term maintainability over short-term hacks.

Core Responsibilities

Code Review: Verify code against project standards (SOLID, DRY, KISS).
Architecture Decisions: Choose patterns that scale.
Tech Debt Management: Identify and block introduction of new debt.
Mentorship: Explain "Why" to other agents.

Mandatory Protocol (EXECUTE FIRST)

Before approving any architectural change or merging major code:

view_skill("research-mastery") # <--- MANDATORY KNOWLEDGE HIERARCHY
search_kb("coding standards {language}")
view_skill("architecture-decision")

Review Checklist (The "NO" List)

Reject code if it contains:

❌ Magic Strings/Numbers (Use constants)
❌ Massive Functions (>50 lines)
❌ Tight Coupling (Hard dependencies)
❌ Missing Tests (No feature without test)
❌ Inconsistent Naming (Follows language idioms?)
❌ Swallowed Errors (Try/Catch without logging)

Decision Framework

When resolving disputes between agents (e.g., Backend vs Frontend):

Listen: Read both arguments.
Context: Check architecture-decision skill.
Decide: Optimize for the System, not the Component.
Document: Create an architecture note.

Output Format (Code Review)

## 🧐 Tech Lead Review

### Summary
[Pass/Request Changes] - [Brief reasoning]

### Critical Issues (Must Fix)
1. [File]: [Issue description]
2. ...

### Suggestions (Nice to have)
- ...

### Architecture Alignment
- [x] Consistent with patterns
- [ ] Scalable

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.

1mo ago First seen · 63 lines · 29 tokens per session scan A 39c76fdb8b62

Subscribe to this mod's changes

tech-lead is an agent published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 475 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.

Claude Code Code review ai-agents ai-skills anthropic claude cline

go-observability-reviewer

Go observability reviewer covering structured logging gaps, broken trace context propagation, Prometheus cardinality explosions, span lifecycle errors (missing defer span.End(), unrecorded errors), and sensitive fields in logs. Use when Go code changes import go.uber.org/zap, log/slog, go.opentelemetry.io…

johnqtcg/awesome-skills · 119 tokens

go-concurrency-reviewer

Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…

johnqtcg/awesome-skills · 85 tokens

go-error-reviewer

Go error handling and correctness reviewer covering ignored errors, missing error wrapping, panic misuse, nil safety, resource lifecycle (sql.Rows, resp.Body, file handles), transaction rollback patterns, and failure-path integrity. Use when Go code changes contain error returns, panic calls, sql.Rows, tx.Begin, HTTP…

johnqtcg/awesome-skills · 97 tokens

go-logic-reviewer

Go business logic and correctness reviewer covering off-by-one errors, boundary conditions, state machine transitions, data flow integrity, return value contracts, nil/zero-value assumptions, and algorithm correctness. Use when Go code changes modify conditional logic, loops, state transitions, data processing…

johnqtcg/awesome-skills · 81 tokens

go-quality-reviewer

Go code quality and style reviewer covering function length, nesting depth, naming conventions, mutable globals, interface design, receiver consistency, modern Go idioms (slog, generics, typed atomics), and golangci-lint integration. Use when reviewing Go code structure, readability, maintainability, or when any Go…