Borrowing it
Nothing to install: this file belongs to adhocteam/recreation-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/adhocteam/recreation-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/adhocteam/recreation-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/adhocteam/recreation-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/adhocteam/recreation-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/adhocteam/recreation-mcp-server/agents-md.svg" alt="Measured on agentmods" 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.02464 | $0.02464 |
| Opus 5 | $0.01232 | $0.01232 |
| Sonnet 5 | $0.00493 | $0.00493 |
| Haiku 4.5 | $0.00246 | $0.00246 |
Grade A, and why
recreation-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines for Recreation MCP Server
This document provides guidance for AI coding assistants working on this project. It captures the conventions, patterns, and practices established during development.
Project Philosophy
Clean, Simple, Fast - The guiding principle for all code:
- Clean: Easy to read and understand
- Simple: Minimal complexity, straightforward solutions
- Fast: Performance matters, but clarity comes first
Architecture Patterns
Project Structure
recreation-mcp-server/
├── cmd/server/ # Application entry point
├── internal/ # Private application code
│ ├── api/ # External API clients (NPS, Recreation.gov, Weather)
│ ├── cache/ # Caching layer with TTL/LRU
│ ├── config/ # Configuration management
│ ├── mcp/ # MCP protocol implementation
│ └── models/ # Shared data types
├── pkg/util/ # Public utility packages
├── testdata/ # Test fixtures (JSON responses)
├── docs/ # GitHub Pages website
└── scripts/ # Helper scripts for testing
Code Organization Principles
-
Internal vs Public: All application logic lives in
internal/. Only truly reusable utilities go inpkg/. -
API Clients: Each external API gets its own file in
internal/api/:nps.go- National Park Servicerecreation.go- Recreation.govweather.go- OpenWeatherMap
-
MCP Layer: Separated into two files:
server.go- Server setup and tool registrationhandlers.go- Tool implementations and schemas
-
Test Files: Co-located with source files using
_test.gosuffix
Code Conventions
Error Handling
- Always return errors, don't panic
- Wrap errors with context:
fmt.Errorf("failed to fetch parks: %w", err) - Log errors before returning them to users
- Use MCP-compliant error responses with error codes
Naming Conventions
- Files: Snake case (e.g.,
http_client.go) - Packages: Single word, lowercase (e.g.,
cache,config) - Structs: PascalCase (e.g.,
SearchParksInput) - Functions: camelCase for private, PascalCase for exported
- Constants: PascalCase (e.g.,
DefaultCacheTTL)
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.
- 7d ago First seen · 353 lines · 2,464 tokens per session scan A ffd164e1444d
recreation-mcp-server AGENTS.md is an instructions file published in the GitHub repository adhocteam/recreation-mcp-server (8 stars, last pushed 20d ago), licensed MIT. It adds 2,464 tokens to every session, about $0.0123 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.
Other instructions, from other repositories
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.
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.
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).
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.