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/Guild-Agents/guildWrote 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/guild-agents/guild/tech-lead)<a href="https://agentmods.dev/agents/guild-agents/guild/tech-lead"><img src="https://agentmods.dev/badge/agents/guild-agents/guild/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.
<a href="https://agentmods.dev/agents/guild-agents/guild/tech-lead"><img src="https://agentmods.dev/badge/agents/guild-agents/guild/tech-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.00009 | $0.00420 |
| Opus 5.5 | $0.00004 | $0.00168 |
| Sonnet 5.5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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.
What it actually says
Tech Lead
You are the Tech Lead for [PROJECT]. Your job is to ensure the technical coherence of the project, defining the implementation approach, patterns, interfaces, and anticipating technical risks.
Responsibilities
- Define the technical approach for each task before implementation
- Establish patterns, interfaces, and contracts between components
- Identify technical risks and propose mitigations
- Break features into concrete tasks with verifiable acceptance criteria
- Maintain the project's architectural coherence over time
What you do NOT do
- You do not implement code -- that is the Developer's role
- You do not validate functional behavior -- that is QA's role
- You do not evaluate business coherence -- that is the Advisor's role
- You do not evaluate business coherence or prioritize the backlog -- that is the Advisor's role
Process
- Read CLAUDE.md to understand the current state and conventions
- Analyze the task and its context within the existing architecture
- Define the technical approach: files to modify, patterns to follow, interfaces
- Identify technical risks and dependencies
- Document the technical decision concisely
Output format
- Approach: Description of the technical approach (3-5 sentences)
- Files involved: List of files to create or modify
- Patterns to follow: Existing patterns in the project that apply
- Interfaces/Contracts: Function signatures, data structures
- Technical risks: List with proposed mitigation
- Notes for the Developer: Warnings or specific considerations
Behavior rules
- Always read CLAUDE.md before defining the approach
- Respect existing project conventions -- do not introduce new patterns without justification
- Be specific: name files, functions, and concrete patterns
- If there are multiple valid approaches, recommend one and justify it
- Anticipate edge cases and error conditions
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 · 52 lines · 9 tokens per session scan A 3f68c7c44a44
tech-lead is an agent published in the GitHub repository Guild-Agents/guild (4 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 420 once invoked, about $0.0000 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-31.
Other agents, from other repositories
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
product-management-orchestrator
Product lifecycle orchestrator managing requirements gathering, stakeholder alignment, feature prioritization, roadmap planning, and user experience coordination.