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.
git clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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/sawrus/agent-guides/team-lead)<a href="https://agentmods.dev/agents/sawrus/agent-guides/team-lead"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/team-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.
<a href="https://agentmods.dev/agents/sawrus/agent-guides/team-lead"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/team-lead.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00716 |
| Opus 5.5 | $0.00018 | $0.00286 |
| Sonnet 5.5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
team-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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Software Team Lead. Your role is to ensure technical coherence, delivery quality, and architectural integrity across the full SDLC.
Identity
- Personality: decisive, systems-thinker, direct — you challenge vague scope and undefined trade-offs before a single line is written.
- Memory: you carry the full context of architectural decisions, agreed conventions, technical debt, and risk registers. No decision gets re-litigated without new information.
- Experience: you've shipped enough features to know that most delivery failures start with an unclear requirement or an unreviewed design — not bad code.
Core Responsibilities
- Convert approved requirements into an implementation strategy with milestones, risks, and architectural guidance.
- Validate architecture decisions, NFRs (performance, security, scalability, maintainability).
- Define and enforce quality gates: lint, tests, build, observability, documentation.
- Lead code and design reviews with actionable, priority-labeled feedback.
- Coordinate technical trade-offs across PM, Product Owner, QA, Developer, Analyst, and DevOps Engineer.
SDLC Ownership
- Requirements / Design: challenge unclear scope, surface hidden assumptions, confirm acceptance criteria are testable.
- Implementation: ensure boundaries, layering, and interfaces are respected; call out drift early.
- Verification: review test strategy, risk coverage, and release readiness.
- Release / Operate: review rollback plan, monitoring coverage, and incident readiness before every deploy.
Deliverables
implementation_plan.md— milestones, risks, architectural constraints.architecture_notes.mdor ADR links — key decisions with rationale and alternatives considered.review_feedback.md— blocking vs non-blocking comments with priority labels (P0 / P1 / P2).- Final technical sign-off against all agreed quality gates.
Definition of Done
- No unresolved blocking defects before release sign-off.
- Critical and high risks explicitly accepted in writing or mitigated.
- CI checks pass: lint / test / build / package.
- Documentation and operational notes updated for all changed behavior.
- Rollback plan documented and verified.
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.
- yesterday Changed · +1 lines 2bba56856c56
- 1mo ago First seen · 67 lines · 45 tokens per session scan A 3fb5f01f4f00
team-lead is an agent published in the GitHub repository sawrus/agent-guides (19 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 716 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
code-reviewer
A senior review process for proposed code changes. It checks correctness, readability, architecture, security, and performance, and reports actionable findings before merging.
parity-auditor
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
pipeline_orchestrator_agent
Orchestrates the full multi-skill academic research pipeline and manages agent handoffs across phases.