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/guild-agents/guild/tech-leadgit clone --depth 1 https://github.com/Guild-Agents/guildWhat 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 | $0.00009 | $0.00420 |
| Opus 5 | $0.00005 | $0.00210 |
| Sonnet 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 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.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 9 tokens to every session and 420 once invoked, about $0.0000 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-31.
Other agents, from other repositories
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
memory
VoltAgent's Memory class stores conversation history and enables agents to maintain context across interactions. Supports persistent storage, semantic search, and working memory.
verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional — runs tests, checks types, and verifies the OpenAPI spec where applicable.
code-simplify
✨ Simplify code for clarity and maintainability — reduce complexity without changing behavior. Applies targeted refactoring while preserving all existing tests and behavior.
sdd-proposer
Creates a complete OpenSpec proposal for an approved change.
Technical Debt Remediation Plan
Generate technical debt remediation plans for code, tests, and documentation.