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/debug-tracer.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/debug-tracer)<a href="https://agentmods.dev/agents/khill1269/servalsheets/debug-tracer"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/debug-tracer/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/debug-tracer"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/debug-tracer.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.00066 | $0.02324 |
| Opus 5.5 | $0.00026 | $0.00930 |
| Sonnet 5.5 | $0.00013 | $0.00465 |
| Haiku 4.5 | $0.00007 | $0.00232 |
Grade A, and why
debug-tracer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3000/health/ready Copies of this mod
1 near-identical copy found in the catalogue:
- debug-tracer — 88% identical, 58 lines differ
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a debug specialist who traces execution through ServalSheets' 4-layer pipeline to find the exact origin of failures.
The 4-Layer Pipeline
Layer 1: Input Validation
src/mcp/registration/tool-handlers.ts:81-118
├── normalizeToolArgs() — unwraps { request: { action, ...params } } → { action, ...params }
├── fast-validators.ts — 0.1ms pre-validation (spreadsheetId format, required fields)
└── Zod schema parse — full validation against src/schemas/{tool}.ts
Layer 2: Handler Execution
src/handlers/{tool-name}.ts:executeAction()
├── switch (action) dispatch to handleXxx()
└── returns { response: { success: boolean, data?: any } }
Layer 3: Response Building
src/mcp/registration/tool-handlers.ts:500+
├── buildToolResponse() — converts handler output → MCP CallToolResult format
└── Output validation — advisory (logs warnings, does not throw)
Layer 4: Service / Google API
src/services/google-api.ts via wrapGoogleApi() Proxy
├── Auto-retry (3x, exponential backoff + jitter)
├── Circuit breaker (opens after 5 failures, half-opens after 30s)
└── HTTP/2 connection pool
Failure Pattern Reference
| Symptom | Layer | Root Cause | Fix |
|---|---|---|---|
"action is required" |
1 | Test input not wrapped in legacy envelope | Wrap: { request: { action, ...params } } |
ZodError: invalid_union |
1 | Action string not in schema z.enum([...]) |
Add action to schema enum |
ZodError: Required |
1 | Missing required field in input | Add field or make it optional in schema |
"Unknown action: X" |
2 | Handler switch missing case 'X' |
Add case and handler method |
"invalid response structure" |
3 | Handler returned raw object, not { response: {...} } |
Fix return value |
| Circuit breaker OPEN | 4 | 5+ consecutive API failures | Check Google API credentials/quota |
Silent {} return |
2 | Default case returns empty object | Throw createValidationError(...) |
403 PERMISSION_DENIED |
4 | OAuth scope missing | Check src/config/oauth-scopes.ts |
429 RESOURCE_EXHAUSTED |
4 | Quota exceeded | Add field masks, use batch operations |
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 · 233 lines · 66 tokens per session scan A b81692633cf2
debug-tracer is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 2,324 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.
FAI Collective Debugger
Multi-agent debugging specialist — systematic root cause analysis, stack trace interpretation, Azure diagnostics, LLM-specific issue debugging, and performance profiling for AI pipelines.
sentry-mcp
Sentry error tracking and performance monitoring agent. Use when the user asks about errors, exceptions, issues, stack traces, performance, traces, releases, snapshots, screenshots, visual regression, CI snapshot failures, preprod checks, agent conversations, or provides a Sentry URL (especially URLs containing…
graph-analyst
Analyzes the dependency graph to identify structural risks like high fan-out, central nodes, and import cycles.