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/servalsheets-implementation.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/servalsheets-implementation)<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/servalsheets-implementation"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/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-v2/servalsheets-implementation"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/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.01249 |
| Opus 5.5 | $0.00028 | $0.00500 |
| Sonnet 5.5 | $0.00014 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
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.
This is a copy
86% identical to servalsheets-implementation — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 22 tools, 342 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 gates:g0 # Baseline integrity
npm run gates:g1 # Metadata consistency (if schema changed)
# 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 gates:g0 && npm run gates:g1
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 6184a620cd0a
servalsheets-implementation is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,249 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to servalsheets-implementation, differing in 28 lines, and is treated as a copy.
Other agents, from other repositories
elite-developer
Principal Full-Stack Engineer. Deterministic implementation engine. Master of TDD, formal verification, and architectural minimalism.
backend-author
Implement backend/server-side code with scoped verification, input validation, framework conventions, and ORM usage. Reads tech stack from {{PROJECTDIR}}/.codearbiter/tech-stack.md.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
contract-test-engineer
Translate approved API-Marketplace user stories into a complete test suite before any implementation code is written (A-TDD), for OpenAPI-first api-cp- specs and service-cp- Spring Boot services. Targets Pact consumer-driven contracts, Spring Boot Test + TestContainers, and WireMock — NOT Serenity/Protractor UI tests…
impl-backend
Implements the backend half of one vertical slice via TDD against its ACs and frozen contract (e.g. "SLICE-01 backend half"), or bootstraps a new backend (scope "project scaffold"). Never touches other slices.
springboot
Implements Spring Boot 3.x applications. Receives failing tests, makes them pass.