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/wsdot-mcp-server --skill wsdot-guidegit clone --depth 1 https://github.com/cyanheads/wsdot-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/wsdot-mcp-server/wsdot-guide)<a href="https://agentmods.dev/skills/cyanheads/wsdot-mcp-server/wsdot-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/wsdot-mcp-server/wsdot-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/wsdot-mcp-server/wsdot-guide"><img src="https://agentmods.dev/badge/skills/cyanheads/wsdot-mcp-server/wsdot-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.00042 | $0.00604 |
| Opus 5.5 | $0.00017 | $0.00242 |
| Sonnet 5.5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
wsdot-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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
Use WSDOT's ferry tools for published sailings and current operating conditions. They do not quote fares, buy tickets, or make vehicle reservations. Highway conditions, tolls, cameras, and border waits use the other wsdot_* tools; they do not establish ferry service.
Gates
- Establish the requested travel date and direction before selecting a sailing. Use the terminal lookup and date-specific route pairs described by the tools; do not assume the reverse direction has the same departures.
- Read each candidate sailing's resolved annotations and the pair-wide sailing notes before recommending it for a car. Do not infer vehicle eligibility from a loading-rule number alone.
- Check ferry alerts before claiming a scheduled sailing will run. Read the full bulletin body for replacements and restrictions, include fleet-wide alerts, and retain unresolved route IDs as unresolved coverage. A date's route list does not cover every seasonal or interisland alert ID.
- Match live space to the departure and intended destination IDs. An itinerary label can name multiple stops or the departure terminal; it does not identify the destination by itself.
- Keep cancellation state and space-reporting flags with the counts. A missing or unreported count does not mean zero, and a positive count is a current observation rather than a boarding guarantee.
- If WSF rejects a date or reports no routes loaded for it, report that schedule coverage limit. Do not conclude that the crossing never operates.
Workflows
Choose a sailing for a vehicle trip
Find the date's directed terminal pair with wsdot_get_ferry_routes, then read wsdot_get_ferry_schedule. Resolve the candidate sailings' annotation indexes against the returned annotations, including the pair-wide notes. Combine that eligibility evidence with wsdot_get_ferry_alerts; the schedule has no per-sailing cancellation flag and alerts apply to routes rather than identifying every affected departure.
Assess the next departure
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 · 34 lines · 42 tokens per session scan A 94c436950f5e
wsdot-guide is a skill published in the GitHub repository cyanheads/wsdot-mcp-server (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 42 tokens to every session and 604 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
wikipedia-guide
Gates and identifier chains for the wikipedia tools. Covers switching language editions without reusing titles, disambiguation pages the article tools don't flag, section numbers versus sectionindex, coverage that differs by edition, and the checks to run before calling something absent or sourced. Use when a…
wikidata-guide
Use wikidata tools to identify entities, verify qualified claims, join external identifiers, and build SPARQL graph queries. Use for Wikidata research that needs identity disambiguation, statement evidence, or completeness checks.
openstates-guide
Identifier chains and gates for the openstates tools (US state legislatures via Open States). Use when tracing a state bill's fate, votes, or sponsors; finding who represents a location and their committees; finding hearings; or comparing states. Read before naming a bill, reporting who voted how, or concluding that a…
onebusaway-guide
Resolve and interpret onebusaway transit results when choosing a boarding stop, tracking a route or trip, checking disruptions, or reading service-day schedules. Use for multi-step questions where direction, agency, missing telemetry, or scheduled versus predicted times change the answer.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
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…