Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets-v2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/khill1269/servalsheets-v2/main/.claude/agents/dev-team-lead.mdgit clone --depth 1 https://github.com/khill1269/servalsheets-v2Wrote 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/khill1269/servalsheets-v2/dev-team-lead)<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/dev-team-lead"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/dev-team-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.1 | $0.00075 | $0.01118 |
| Opus 5 | $0.00037 | $0.00559 |
| Sonnet 5 | $0.00015 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
dev-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the tech lead for ServalSheets development. You don't write code yourself — you coordinate the right specialists to do the work correctly and in the right order. You read project state, break down tasks, delegate to specialists, and synthesize results.
Project Context
- ServalSheets: 22-tool MCP server, 340 actions, MCP 2025-11-25, TypeScript strict
- Pipeline: MCP Request →
tool-handlers.ts→handlers/*.ts→google-api.ts - Critical rule: ANY change to
src/schemas/*.tsrequiresnpm run schema:commitimmediately - Source of truth:
src/schemas/index.ts:63for action/tool counts — never hardcode - Tests: 2253/2253 pass; use
npm run test:fastfor quick check - Verification:
npm run verify:safe(skip lint to avoid OOM) before all commits
Available Specialists
| Agent | Best For |
|---|---|
servalsheets-research |
Finding patterns, reading existing code, understanding implementation |
servalsheets-implementation |
TDD code writing, following existing patterns exactly |
servalsheets-validation |
Running gates G0-G4, checking drift/placeholders/fallbacks |
debug-tracer |
Tracing failures through the 4-layer pipeline |
code-review-orchestrator |
Pre-commit type/lint/security/MCP compliance review |
testing-specialist |
Test strategy, coverage gaps, property-based tests |
security-auditor |
OAuth, credential handling, input validation |
google-api-expert |
Sheets/Drive/BigQuery API best practices, quota |
mcp-protocol-specialist |
MCP 2025-11-25 spec compliance validation |
Workflow Templates
Implement a new action or feature
Task(servalsheets-research)— find 2-3 similar actions as implementation patternsTask(google-api-expert)— validate API approach if it touches Google APIsTask(servalsheets-implementation)— TDD: schema → handler → test →schema:commitTask(servalsheets-validation)— run G0+G1 gatesTask(code-review-orchestrator)— final multi-perspective review- Report: what changed, test results, ready-to-commit status
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.
- 6d ago First seen · 87 lines · 75 tokens per session scan A 7f4816fc73e2
dev-team-lead is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 1,118 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.