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 instructions/ruby0606/mcp-earthquake-server/copilot-instructionsgit clone --depth 1 https://github.com/ruby0606/mcp-earthquake-serverWhat 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.01021 | $0.01021 |
| Opus 5 | $0.00511 | $0.00511 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade C, and why
mcp-earthquake-server copilot-instructions.md scanned grade C 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 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- GitHub Copilot Instructions for MCP Earthquake Monitoring Server --> How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJECT STATUS: PRODUCTION READY
COPILOT CONTEXT:
When working on this project:
- Data Sources: Always respect attribution requirements and usage terms
- Global Scope: Support worldwide coordinates, no geographic restrictions
- Error Handling: Implement proper validation for seismological parameters
- Performance: Consider API rate limits and caching strategies
- Scientific Accuracy: Cross-reference multiple sources when possible
- Emergency Use: Note this is for research only, not emergency response
- Data Integrity: Always use real API calls, don't use mock data
COMPLETED MILESTONES:
- Project Requirements Clarified - Global earthquake monitoring via MCP server
- Project Scaffolded - Complete TypeScript MCP server implementation
- Multi-source Integration - IRIS + USGS + GNSS + InSAR data providers
- Global Coverage Implemented - Worldwide earthquake monitoring (no geographic limits)
- Code Review Completed - All critical issues resolved
- Comprehensive Documentation - README, Developer Setup, Research Guide
- Data Attribution Added - Proper citations and usage terms for all sources
- GitHub Repository Live - https://github.com/ruby0606/mcp-earthquake-server
- Testing Validated - Real data retrieval confirmed from all sources
- Production Deployment Ready - MIT licensed, open source distribution
🎯 MCP EARTHQUAKE MONITORING SERVER
Repository: https://github.com/ruby0606/mcp-earthquake-server
This is a production-ready Model Context Protocol server providing AI systems with direct access to authoritative earthquake data sources, eliminating hallucinations and ensuring scientific accuracy.
🔧 TECHNICAL ARCHITECTURE:
Core Implementation: src/index.ts - Main MCP server with 10 earthquake monitoring tools
Data Providers:
src/providers/iris-provider.ts- IRIS seismological data (FIXED: text format parsing)src/providers/usgs-provider.ts- USGS real-time earthquake feedssrc/providers/gnss-provider.ts- GPS/GNSS crustal deformation datasrc/providers/insar-provider.ts- Satellite radar interferometry data
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 · 95 lines · 1,021 tokens per session scan C 0375d08d0958
mcp-earthquake-server copilot-instructions.md is an instructions file published in the GitHub repository ruby0606/mcp-earthquake-server (1 stars, last pushed 1y ago), licensed MIT. It adds 1,021 tokens to every session, about $0.0051 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.