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.
git clone --depth 1 https://github.com/Waybox-AI/roadtrip-skillWrote 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/commands/waybox-ai/roadtrip-skill/roadtrip)<a href="https://agentmods.dev/commands/waybox-ai/roadtrip-skill/roadtrip"><img src="https://agentmods.dev/badge/commands/waybox-ai/roadtrip-skill/roadtrip/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/commands/waybox-ai/roadtrip-skill/roadtrip"><img src="https://agentmods.dev/badge/commands/waybox-ai/roadtrip-skill/roadtrip.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.00015 | $0.00214 |
| Opus 5 | $0.00008 | $0.00107 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
roadtrip 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 12d 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.
What it actually says
Invoke the roadtrip-navigator skill and follow its full SKILL.md workflow to
handle this road-trip request: detect the entry mode (plan-from-scratch vs.
verify-an-existing-route), segment the drive into sane daily legs, research
stops / fuel / EV-charging / national-park reservations, build the reservation
countdown and reliability-graded budget, and render the map-first single-file
HTML itinerary.
User request: $ARGUMENTS
If the request above is empty or missing required slots — start location,
destination or region, number of days, party size, vehicle / fuel type, travel
month — run the skill's scripts/helper.py slot check and ask the user for the
missing pieces first, then proceed with planning.
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.
- 12d ago First seen · 20 lines · 15 tokens per session scan A 470910940845
roadtrip is a command published in the GitHub repository Waybox-AI/roadtrip-skill (123 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 214 once invoked, about $0.0001 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-30.
Other commands, from other repositories
pitchcraft.zh-CN
A Chinese-language installation command for the pitchcraft skill, which structures persuasive briefings and reports. It copies the Chinese or English skill file into Claude Code's skills folder.
drupal
Perform comprehensive Drupal 11 code audit and security analysis.
semantic-change-check
Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks.
cleanup
Run a systematic cleanup on the provided code to resolve smells, simplify complexity, and enforce best practices.
refactor-plan
Draft a step-by-step refactoring strategy for complex code changes to ensure behavior is preserved.
workflow-router
Route to the appropriate spec-driven workflow command based on the user's intent.