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 redhuntlabs/wizard --skill planning-a-tripgit clone --depth 1 https://github.com/redhuntlabs/wizardWrote 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/redhuntlabs/wizard/planning-a-trip)<a href="https://agentmods.dev/skills/redhuntlabs/wizard/planning-a-trip"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/planning-a-trip.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.00021 | $0.00851 |
| Opus 5 | $0.00010 | $0.00426 |
| Sonnet 5 | $0.00004 | $0.00170 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
planning-a-trip 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning a Trip
What this does
Walks you from a vague trip idea to a complete plan: dates, route, lodging, daily structure, and a packing list — without overplanning the things that don't matter.
When to use
- Planning a personal trip (vacation, family visit, weekend away)
- Planning a work trip (conference, customer visit, offsite)
- Planning the logistics of a trip you've already committed to
What you bring (Inputs)
- Destination(s) and rough dates
- Trip purpose (rest / explore / event / mixed)
- Constraints (budget, dietary, accessibility, kids, pets)
- Anchor commitments (flights you've booked, events you must attend)
What you get (Output)
A trip plan: dates + transport + lodging + day-by-day skeleton + packing checklist + a small "open questions" list.
How it works (Steps)
This is a guided workflow.
Stages
Stage 1: Anchor
Lock the immovable: dates, must-attend events, return-by deadline.
Stage 2: Route and transport
Pick lodging-to-event transport (walk / transit / rental car / rideshare). Book the longest, hardest piece first (long flights, train passes).
Stage 3: Lodging
Pick lodging by criteria in this order: proximity to anchor events, sleep quality (reviews mention noise / bed), then price. Book.
Stage 4: Day-by-day skeleton
For each day, write 1-2 anchors (event, meal, sight) and leave the rest open. Overplanning produces brittle trips.
Stage 5: Packing checklist
Generate a checklist by category: docs, electronics, clothes (per weather), toiletries, meds, comfort items.
Stage 6: Open questions
List what you couldn't decide yet (e.g., "decide on dinner spots day-of"). Naming them prevents anxiety.
Checkpoints
- After Stage 1: dates and anchors locked
- After Stage 2: long-haul transport booked
- After Stage 3: lodging confirmed
- After Stage 4: each day has 1-2 anchors and free time
- After Stage 5: checklist exists
- After Stage 6: open questions captured
Loop-back conditions
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 · 108 lines · 21 tokens per session scan A 045f671a5aeb
planning-a-trip is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 851 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-31.
Other skills, from other repositories
fastapi
A Python framework for building web APIs, which are interfaces that let programs communicate over HTTP. It supports request validation, automatic API documentation, asynchronous code, reusable dependencies, and common authentication methods.
fzf
A command-line tool for finding items by typing partial text, with results updating as you type. It can search files, shell command history, processes, directories, Git branches, commits, and other text output.
glances
A guide for using Glances, a cross-platform system-monitoring tool that displays computer resource and process information in a terminal, browser, or API.
lazydocker
A keyboard-driven terminal interface for managing Docker, a system for running applications in isolated containers.
paper-checking
A Windows application for finding copied text in documents. It compares files with a reference collection or compares documents in the same batch with one another.
you-get
A command-line tool for downloading videos, audio, and images from websites such as YouTube and Bilibili.