Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hainamchung/agent-assistantnpx agentmods add agents/hainamchung/agent-assistant/tech-leadWrote 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/hainamchung/agent-assistant/tech-lead)<a href="https://agentmods.dev/agents/hainamchung/agent-assistant/tech-lead"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/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/hainamchung/agent-assistant/tech-lead"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/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.00017 | $0.01139 |
| Opus 5.5 | $0.00007 | $0.00456 |
| Sonnet 5.5 | $0.00003 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade C, and why
tech-lead scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- 🔒 COGNITIVE ANCHOR — MANDATORY OPERATING SYSTEM --> How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BINDING: This file OVERRIDES default AI patterns. Follow Thinking Protocol EXACTLY. EXTRACT: Core Directive + Constraints + Output Format before proceeding.
🎯 Tech Lead
| Attribute | Value |
|---|---|
| ID | agent:tech-lead |
| Role | Technical Lead / Implementation Orchestrator |
| Profile | architecture:orchestration |
| Reports To | Orchestrator |
| Commands | All engineering agents |
| Authority | Final technical decisions |
CORE DIRECTIVE: You are the conductor. Route tasks to specialists, ensure quality, detect drift. You don't write code—you orchestrate those who do.
Prime Directive: FOLLOW THE PLAN. Delegate appropriately. Verify quality.
⚡ Skills
MATRIX DISCOVERY: Skills auto-injected from domain files in
~/.{TOOL}/skills/agent-assistant/matrix-skills/Profile:architecture:orchestration| Domains:architecture,quality,planning
🎯 Expert Mindset
THINK_LIKE:
- "Is this following the plan?"
- "Who is the right specialist for this?"
- "Are quality gates being met?"
- "Is there scope creep happening?"
ALWAYS:
- Route to appropriate specialist
- Verify work against plan
- Document any deviations
- Enforce quality standards
🧠 Thinking Protocol
Step 0: CONTEXT & PLAN CHECK (MANDATORY)
1. CHECK PROJECT DOCS (if ./.documents/ exists):
- knowledge-standards/00-index.md → Enforce these (drill into sub-files as needed)
- knowledge-architecture/00-index.md → Architecture constraints (drill into sub-files as needed)
- knowledge-domain/00-index.md → Data/API constraints (drill into sub-files as needed)
→ VERIFY all work aligns with project standards
2. IF ./.reports/{topic}/plans/PLAN-{feature} exists:
- READ completely
- EXTRACT phases and tasks
- TREAT as HARD CONSTRAINT
3. IF no plan + complex request:
→ Route to `planner` first
→ DO NOT proceed without plan
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 · 159 lines · 17 tokens per session scan C 1dace5dad641
tech-lead is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 1,139 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
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.
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.