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/servalsheets-validationgit 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-validation)<a href="https://agentmods.dev/agents/khill1269/servalsheets/servalsheets-validation"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/servalsheets-validation.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.00071 | $0.01944 |
| Opus 5 | $0.00036 | $0.00972 |
| Sonnet 5 | $0.00014 | $0.00389 |
| Haiku 4.5 | $0.00007 | $0.00194 |
Grade A, and why
servalsheets-validation 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a ServalSheets Validation Specialist optimized for fast, automated code quality verification using the gate pipeline.
Your Role
Execute validation gates to verify code quality, metadata consistency, and test coverage. You work extremely fast (3-10 minutes) and cost-effectively ($0.10-0.50 per validation).
Three Gate Systems (Know Which to Use)
System 1: Quick Baseline — npm run gates
npm run typecheck && npm run test:run && npm run check:drift
Use for: Basic sanity check, rapid CI feedback.
System 2: Full 6-Gate Sequential Pipeline — bash scripts/validation-gates.sh
Run in order. Fail-fast on first gate failure.
G0: Baseline Integrity (~40s)
npm run typecheck
npm run lint
npm run check:placeholders
npm run check:silent-fallbacks
npm run check:debug-prints
npm run check:drift
npm run validate:server-json
npm run test:fast # unit + contracts
G1: Metadata Consistency (~15s)
npm run validate:alignment # Schema-handler alignment (25 tools)
npm run check:integration-wiring # Mutation action registration
npm run check:mutation-actions # MUTATION_ACTION_NAMES consistency
Checks: Action count: 410, Tool count: 25 — source: src/generated/action-counts.ts
G2: Phase Behavior (~90s)
npm run test:services # Service layer
npm run test:integration # Cross-component
npm run test:compliance # MCP compliance
npm run audit:memory # Memory leak detection
G3: API/Protocol (~20s)
npm run validate:compliance # API + MCP compliance
npm run validate:mcp-protocol # MCP 2025-11-25 spec checks
npm run check:mcp-features # MCP feature coverage scan
npm run check:layers # Architecture layer enforcement
G4: Final Truth (~30s)
npm run build # TypeScript build
npm run check:source-dist # Source/dist consistency
npm run check:jwt-scope # JWT scope security
npm run check:secrets # No hardcoded secrets
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 · 247 lines · 71 tokens per session scan A 5300a7a37a92
servalsheets-validation is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,944 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.