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 skills add cyanheads/national-parks-mcp-server --skill national-parks-guidegit clone --depth 1 https://github.com/cyanheads/national-parks-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/skills/cyanheads/national-parks-mcp-server/national-parks-guide)<a href="https://agentmods.dev/skills/cyanheads/national-parks-mcp-server/national-parks-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/national-parks-mcp-server/national-parks-guide/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/skills/cyanheads/national-parks-mcp-server/national-parks-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/national-parks-mcp-server/national-parks-guide.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.00048 | $0.00627 |
| Opus 5.5 | $0.00019 | $0.00251 |
| Sonnet 5.5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
national-parks-guide 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
Use these tools to assess NPS destinations and assemble a visit plan. Campground records describe facilities and reservation arrangements; they do not report vacancies for travel dates or make bookings. Proximity, driving routes, and live forecasts require other sources.
Identifiers
Carry the selected park's parkCode from nps_find_parks through the trip. Alert, campground, activity, and event IDs identify their own records; they are not substitutes for a park code.
Gates
- Confirm the returned name, state, and designation match the intended destination before requesting related records. Search ranking cannot settle an ambiguous name: Glacier and Glacier Bay can both match "glacier".
- Check the selected park's alerts before recommending access-dependent activities. Read the affected location and condition, not just the category; a filtered search cannot establish that the whole park is clear.
- Check result notices and coverage before concluding something is absent. A partial result, an upstream warning, or an empty page beyond the matches cannot support that conclusion. An empty curated activity or event feed does not establish that the park offers nothing to do.
- Verify date-specific availability through the campground's reservation source before calling a campsite available. Reservable and first-come counts describe inventory, not remaining sites.
- Verify hookup requirements on the campground's linked page. RV permission, a dump station, and potable water do not establish an RV hookup.
- Place a recurring event on the itinerary only when its returned occurrence dates include the visit date. A series anchor is not evidence of an occurrence that day; an empty occurrence list does not establish cancellation.
Workflows
Camping feasibility
Resolve the destination, then combine park access alerts with campground records. Compare the user's actual requirements against amenities, accessibility text, reservation guidance, and linked campground details. Keep unknown amenities unresolved. Present suitable candidates with their reservation links, separating facility suitability from availability for the requested dates.
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 · 40 lines · 48 tokens per session scan A 55562524433c
national-parks-guide is a skill published in the GitHub repository cyanheads/national-parks-mcp-server (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 627 once invoked, about $0.0002 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-10-28.
Other skills, from other repositories
internet-archive-guide
Use ia tools to investigate historical web pages or Internet Archive books and documents. Resolve capture and item identities, compare the captures actually served, and check coverage before claiming content absent or fully read.
oecd-guide
Build SDMX keys, confirm which series an OECD dataflow actually carries, and read oecd results without mixing units, breakdowns, or country aggregates. Use when calling oecd tools for cross-country statistics (GDP, growth, unemployment, labour, education, tax), when a query returns noresults or invalidkey, or when a…
usgs-water-guide
Gates and workflows for the water tools over USGS stream gages and groundwater wells. Covers whether a river or aquifer is high or low right now, telling live gages from discontinued ones, reading depth-to-water rankings (they run inverted), finding the parameter code a site actually reports, time zones and data lag…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.