What is Perigee-Tides AGENTS.md?

Repository instructions for Perigee-Tides, a TypeScript MCP server that provides NOAA weather and ocean data tools.

Use them when developing or testing the server, including its water, current, weather, station, and metadata features.

They explain how to build, test, format, and run the server while avoiding mistakes such as writing logs to the protocol output.

How RyanCardin15/Perigee-Tides configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to RyanCardin15/Perigee-Tides. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/RyanCardin15/Perigee-Tides/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/RyanCardin15/Perigee-Tides

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ryancardin15/perigee-tides/agents-md/github.svg)](https://agentmods.dev/instructions/ryancardin15/perigee-tides/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/ryancardin15/perigee-tides/agents-md"><img src="https://agentmods.dev/badge/instructions/ryancardin15/perigee-tides/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ryancardin15/perigee-tides/agents-md"><img src="https://agentmods.dev/badge/instructions/ryancardin15/perigee-tides/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,119 This file is loaded in full into every session.

When invoked 1,119 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01119	$0.01119
Opus 5	$0.00560	$0.00560
Sonnet 5	$0.00224	$0.00224
Haiku 4.5	$0.00112	$0.00112

Measured 8d ago against content hash f3b2d355d412, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

Perigee-Tides 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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

Perigee-Tides CLAUDE.md — 91% identical, 4 lines differ

AGENTS.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.

Development Commands

npm run build - Compile TypeScript to dist/
npm test - Run vitest unit tests (validation, formatting, cache, astronomy)
npm run test:live - End-to-end smoke test: spins up the built server over stdio and exercises every tool against the live NOAA API (scripts/smoke-live.mjs)
npm run inspector - MCP Inspector against dist/index.js
npm run dev - Run from source with tsx
npm run format - Prettier

Always npm run build before npm run test:live — the smoke test runs dist/index.js.

Architecture

MCP server built on the official @modelcontextprotocol/sdk (McpServer + registerTool/registerResource/registerPrompt). Entry point src/index.ts runs stdio by default; --http [--port N] starts a stateless streamable-HTTP endpoint at /mcp.

CRITICAL: never write to stdout. In stdio mode stdout is the JSON-RPC channel; all logging must use console.error.

Layers (dependencies point downward):

src/tools/* — 25 tool registrations grouped by domain (water, currents, met, stations, station-metadata, derived, astronomy, marine-forecast, reference). Each tool: Zod input schema with nuance-carrying .describe() texts, read-only annotations, markdown+json response_format, structuredContent attached, errors returned via respondError (never thrown to the protocol layer).
src/services/* — one module per NOAA API surface (data-api.ts, metadata-api.ts, dpapi.ts) plus local moon-phase-service.ts / sun-service.ts (suncalc).
src/client/http.ts — shared axios layer: 30s timeout, 2 retries with backoff on network/5xx/429, and error mapping that appends actionable hints. The three NOAA APIs fail differently: the Data API and DPAPI return HTTP 200 or 4xx with {"error":{"message"}} bodies; the Metadata API returns bare 404s with no body.
src/client/cache.ts — in-memory TTL cache (station directory 6h, station resources 1h). Nearest-station search is client-side Haversine over the cached directory because MDAPI ignores lat/lon/radius on its list endpoint (verified live).
src/validation/dates.ts — normalizes ISO dates to NOAA formats, enforces the five legal date-param combinations, and pre-validates per-product maximum request spans (see MAX_SPAN_DAYS).
src/format/* — unit labels per measurement (units.ts), flag legends, markdown table/series rendering, CHARACTER_LIMIT truncation.
src/reference/content.ts — curated reference topics served by both the noaa_get_reference_guide tool and noaa://reference/{topic} resources.

Read the full file on GitHub · 52 lines

Changes

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.

8d ago First seen · 52 lines · 1,119 tokens per session scan A f3b2d355d412

Subscribe to this mod's changes

Perigee-Tides AGENTS.md is an instructions file published in the GitHub repository RyanCardin15/Perigee-Tides (6 stars, last pushed 1mo ago), licensed MIT. It adds 1,119 tokens to every session, about $0.0056 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.

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

Perigee-Tides: Instructions file for Codex