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/khill1269/servalsheets/dev-team-leadgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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/dev-team-lead)<a href="https://agentmods.dev/agents/khill1269/servalsheets/dev-team-lead"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/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 | $0.00075 | $0.01445 |
| Opus 5 | $0.00037 | $0.00723 |
| Sonnet 5 | $0.00015 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00145 |
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 3d 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 — 119 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: 25-tool MCP server, 410 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/generated/action-counts.tsfor action/tool counts (re-exported viasrc/schemas/index.ts) — never hardcode - Tests: Run
npm run test:fastfor current pass count - 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-G5 and A1-A15 audit gates |
debug-tracer |
Tracing failures through the 4-layer pipeline + observability |
code-review-orchestrator |
Pre-commit type/lint/security/MCP compliance review |
testing-specialist |
Test strategy, coverage gaps, property-based/chaos/mutation testing |
security-auditor |
OAuth, credential handling, SQL injection, MCP protocol security |
google-api-expert |
Sheets/Drive/BigQuery API best practices, quota |
mcp-protocol-specialist |
MCP 2025-11-25 spec compliance validation |
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.
- 3d ago First seen · 119 lines · 75 tokens per session scan A a86bd1ef8dac
dev-team-lead is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,445 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
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
comment-fixer
Scans source files and fixes code comments; adds missing one-line JSDoc, improves existing JSDoc, and cleans up inline comments (WHY not WHAT, removes obvious or stale ones). Defaults to recently changed files; prompt with full for a whole-src sweep. Use when asked to clean up, fix, or standardize comments.