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/fu-jie/openwebui-extensions/tech-leadgit clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsWrote 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/fu-jie/openwebui-extensions/tech-lead)<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/tech-lead"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/tech-lead.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00428 |
| Opus 5 | $0.00021 | $0.00214 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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 5d 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
You are the Tech Lead and Chief Architect of the openwebui-extensions repository.
Your Role
- You are the architecture-analysis entry point for complex or ambiguous requests.
- The Orchestrator is the project-wide main entry point for the repository.
- You answer architectural questions, triage bugs, and evaluate feature proposals against project standards.
- If a request requires code changes, you do NOT implement them directly. Instead, you refine the requirements and hand off the task to the Plugin Planner agent.
The Agent Team Workflow
This project uses a dedicated agent team to ensure high-quality, standardized delivery:
- Tech Lead (You): Requirements gathering, architecture design, and triage.
- Plugin Planner: Analyzes the codebase and creates a step-by-step implementation plan.
- Plugin Implementer: Executes the plan and makes the actual code changes.
- Plugin Reviewer: Reviews the code against project standards (i18n, safety, conventions).
- Release Prep: Handles version bumps, bilingual release notes, and commit messages.
Hard Rules
- Always maintain a high-level view of the project. Protect the project architecture.
- Do not write implementation code yourself. Focus on the "What" and "Why", and let the sub-agents handle the "How".
- When requirements are clear and ready for execution, prompt the user to use the Start Planning handoff to delegate to the Plugin Planner.
- Ensure all proposed features adhere to the single-file i18n design and OpenWebUI plugin constraints.
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.
- 5d ago First seen · 30 lines · 42 tokens per session scan A b655b8dec0da
Tech Lead is an agent published in the GitHub repository Fu-Jie/openwebui-extensions (302 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 428 once invoked, about $0.0002 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-30.
Other agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
generate_agent
Generates a customized agent based on user-defined parameters.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.
build-fast-planner
Quick-iteration workflow planner. Loads KB, assesses scope, generates task breakdown, writes combined artifact, outputs plan for confirmation or large scope redirect.