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 rules/seeincodes/skyfi-mcp/error-resolution-loggit clone --depth 1 https://github.com/seeincodes/skyfi-mcpWhat 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.00000 | $0.00361 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
error-resolution-log 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 yesterday.
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.
What it actually says
Error Resolution Logging
When to Log
Log to docs/ERROR_FIX_LOG.md when resolving:
- BUILD — TypeScript compilation failures, tsup bundling errors
- MCP — MCP SDK protocol errors, tool registration failures
- SKYFI — SkyFi API integration errors (auth, rate limits, unexpected responses)
- OSM — Nominatim geocoding failures, rate limit issues
- TRANSPORT — STDIO or HTTP+SSE transport errors
- AUTH — Authentication failures, credential validation issues
- VALIDATION — Input validation edge cases, AOI guardrail issues
- ENVELOPE — Response envelope schema violations
- WORKERS — Cloudflare Workers deployment or runtime errors
- TEST — Test infrastructure failures, CI pipeline issues
- WEBHOOK — Webhook delivery failures, event queue issues
- DOCKER — Container build or runtime errors
- Any error that takes > 5 minutes to diagnose
When NOT to Log
- Typos or syntax errors caught immediately
- Linter warnings resolved by auto-fix
- Expected test failures during TDD red phase
- Temporary errors during active development (e.g., missing import while writing new code)
Log Format
### [YYYY-MM-DD] — [CATEGORY] — Brief description
**Error:** Error message or behavior
**Context:** What was being done
**Root Cause:** Why it happened
**Fix:** What was changed
**Prevention:** How to prevent recurrence
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.
- yesterday First seen · 45 lines · 0 tokens per session scan A 182e1c9e02d0
error-resolution-log is a cursor rule published in the GitHub repository seeincodes/skyfi-mcp (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 361 tokens. 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 cursor rules, from other repositories
docs
All documentation files use MDX format with a specific structure.
type-inference
Derive TypeScript types from Zod schemas - no hand-written interfaces for wire shapes.
turborepo
Turbo query graph primitives and signed remote-cache key provisioning.
react
React 19 SPA invariants - client-only, no fetch in useEffect, Compiler memo policy.
workers-cache
Workers Cache - Cache-Control, gateway exports cache off, RPC vs fetch.
git-workflow
Branch hygiene — rebase on main before every PR and keep branches synced.