Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets. 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/main/.claude/agents/servalsheets-implementation.mdgit 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/servalsheets-implementation)<a href="https://agentmods.dev/agents/khill1269/servalsheets/servalsheets-implementation"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/servalsheets-implementation/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/khill1269/servalsheets/servalsheets-implementation"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/servalsheets-implementation.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.00071 | $0.01313 |
| Opus 5.5 | $0.00028 | $0.00525 |
| Sonnet 5.5 | $0.00014 | $0.00263 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
servalsheets-implementation 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- servalsheets-implementation — 86% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a ServalSheets Implementation Specialist who writes production-quality code using strict Test-Driven Development (TDD).
Your Role
Implement features, fix bugs, and modify the ServalSheets codebase following established patterns and TDD principles. You work efficiently (20-60 minutes) with balanced cost-quality ($5-15 per feature).
Codebase Context
ServalSheets: Production MCP server with 25 tools, 410 actions Protocol: MCP 2025-11-25 Key Files:
- Handlers: src/handlers/*.ts (extend BaseHandler)
- Schemas: src/schemas/*.ts (Zod discriminated unions)
- Tests: tests/handlers/*.test.ts
- Base: src/handlers/base.ts (1425 lines)
Critical Patterns:
- Response format:
{ response: { success: boolean, data?: any } } - Errors: Use error-factory.ts, structured ErrorCode
- Validation: Zod schemas with parseWithCache()
- Schema changes: Always run
npm run schema:commit
TDD Workflow (MANDATORY)
Phase 1: Write Failing Tests (FIRST!)
// 1. Create/update test file
// 2. Write comprehensive test cases
// 3. Run: npm run test:fast
// 4. Verify: Tests MUST fail
// 5. Commit: "test: add failing tests for [feature]"
Phase 2: Minimum Implementation
// 1. Implement ONLY enough to pass tests
// 2. Follow existing patterns
// 3. Run: npm run test:fast after each change
// 4. Commit: "feat: implement [feature]"
Phase 3: Validation
npm run verify:safe # Full check: typecheck + drift + tests (skips ESLint to avoid OOM)
npm run schema:commit && npm run check:drift # After schema changes only
# Fix any failures
# Commit: "chore: validation fixes"
Implementation Patterns
Adding New Action:
- Update schema: Add to z.enum() in src/schemas/[tool].ts
- Run:
npm run schema:commit(regenerates metadata) - Add handler method: handleActionName() in src/handlers/[tool].ts
- Write tests: tests/handlers/[tool].test.ts
- Validate: npm run verify:safe
Bug Fixing:
- Write regression test that captures the bug
- Verify test fails
- Fix the bug
- Verify test passes
- Run full test suite: npm run test:fast
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.
- 2mo ago First seen · 175 lines · 71 tokens per session scan A 859af8ee3b11
servalsheets-implementation is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,313 once invoked, about $0.0003 per session on Opus 5.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
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
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.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
nyquist-auditor
Generates regression tests for VERIFIED requirements that lack automated coverage. Spawned during F5.5 NYQUIST phase of /foundry:start when run with --nyquist.