Borrowing it
Nothing to install: this file belongs to cyanheads/earthquake-mcp-server. 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/cyanheads/earthquake-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/cyanheads/earthquake-mcp-serverWrote 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/instructions/cyanheads/earthquake-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/cyanheads/earthquake-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/earthquake-mcp-server/agents-md/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/instructions/cyanheads/earthquake-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/earthquake-mcp-server/agents-md.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.06325 | $0.06325 |
| Opus 5.5 | $0.02530 | $0.02530 |
| Sonnet 5.5 | $0.01265 | $0.01265 |
| Haiku 4.5 | $0.00632 | $0.00632 |
Grade A, and why
earthquake-mcp-server AGENTS.md 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 today.
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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Protocol
Server: earthquake-mcp-server
Package: @cyanheads/earthquake-mcp-server
Version: 0.4.1
Framework: @cyanheads/mcp-ts-core ^0.13.15
Engines: Bun ≥1.4.0, Node ≥24.0.0
MCP SDK: @modelcontextprotocol/server ^2.3.1
Zod: ^4.6.7
Read the framework docs first:
node_modules/@cyanheads/mcp-ts-core/CLAUDE.mdcontains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
What's Next?
When the user asks what's next or needs direction, suggest options based on the current project state. Common next steps:
- Run
devcheck— lint, format, typecheck, and security audit - Add tests — scaffold tests for existing definitions using the
add-testskill - Field-test definitions — exercise tools/resources/prompts with real inputs using the
field-testskill, get a report of issues and pain points - Run the
security-passskill — audit handlers for MCP-specific security gaps: output injection, scope blast radius, input sinks, tenant isolation - Run the
maintenanceskill — investigate changelogs, adopt upstream changes, and sync skills afterbun update --latest - Add tools/resources/prompts — scaffold new definitions using the
add-tool,add-resource,add-promptskills - Run the
polish-docs-metaskill — reconcile README, metadata, and the agent protocol with the implemented surface - Re-run the
setupskill — reconcile project orientation, skills, structure, and metadata - Run the
design-mcp-serverskill — map a new domain surface before implementing it - Add services or app tools — use
add-servicefor integrations andadd-app-toolfor a tool with a paired UI resource
Tailor suggestions to what's actually missing or stale — don't recite the full list every time.
Core Rules
- Logic throws, framework catches. Tool/resource handlers are pure — throw on failure, no
try/catch. PlainErroris fine; the framework catches, classifies, and formats. Use error factories (notFound(),validationError(), etc.) when the error code matters. - Use
ctx.logfor request-scoped logging. Noconsolecalls. - Use
ctx.statefor tenant-scoped storage. Never access persistence directly. - Need input the caller didn't supply?
return ctx.requestInput(...)and readctx.inputswhen the handler is re-entered. Neverawaitfor user input mid-handler. - Secrets in env vars only — never hardcoded.
- Cut noise. Add only what earns its place: no speculative generality, no guards for states the framework already prevents (Zod-validated params, classified errors), no abstraction until a third caller proves it, no option nothing sets.
- Close the loop on issues. When implementing work tracked by a GitHub issue, comment on the issue with what landed and close it. Do both — a comment without a close leaves stale issues open; a close without a comment leaves no record of what shipped. The comment is for future readers — state the concrete changes, not the conversation that produced them.
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.
- today Changed db535046b816
- 7d ago Changed · +5 lines · +249 tokens per session 237be2f44cb0
- 14d ago Changed · -1 lines · +198 tokens per session 9b40fea76f4b
- 28d ago Changed · +3 lines · +86 tokens per session 266ac2195f5a
- 1mo ago First seen · 322 lines · 5,792 tokens per session scan A cd8dbe0ab2ae
earthquake-mcp-server AGENTS.md is an instructions file published in the GitHub repository cyanheads/earthquake-mcp-server (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 6,325 tokens to every session, about $0.0253 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-09-20.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.