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 borski/travel-hacking-toolkit --skill trip-plannergit clone --depth 1 https://github.com/borski/travel-hacking-toolkitWrote 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/borski/travel-hacking-toolkit/trip-planner)<a href="https://agentmods.dev/skills/borski/travel-hacking-toolkit/trip-planner"><img src="https://agentmods.dev/badge/skills/borski/travel-hacking-toolkit/trip-planner.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.02258 |
| Opus 5 | $0.00023 | $0.01129 |
| Sonnet 5 | $0.00009 | $0.00452 |
| Haiku 4.5 | $0.00005 | $0.00226 |
Grade A, and why
trip-planner 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Companion reference skills. Load these for deeper context:
flight-search-strategy— full search workflow and source prioritylessons-learned— Seats.aero workflow and common failure modes (load before any award search)points-valuations— CPP rules, opportunity costpartner-awards— reachability through alliance + bilateral partnershipsaward-sweet-spots— flag legendary redemptionsbooking-guidance— booking flow + phone numbers + the "hold before transfer" ruletransfer-bonuses— live current transfer bonuses (weekly refresh) before recommending any transferstopovers— per-program stopover rules; can turn a one-trip plan into a multi-city itinerary at no extra mileage costaward-holds— per-program hold rules; affects transfer timing decisionsround-the-world— when the trip request implies 3+ stops or multiple regions, RTW products may be cheaper than separate awardsstatus-match— when a user mentions wanting status or asks about elite tier shortcuts; covers free direct matches, paid concierge fees, and once-per-lifetime warnings
Trip Planner
"Plan a trip to Paris Aug 11-15" answered with one complete cost breakdown.
Orchestrates compare-flights, compare-hotels, transfer-partners, and trip-calculator into a unified trip analysis. Shows total trip cost in cash vs every available points strategy.
This is an orchestration skill. It tells the agent which skills to invoke and how to combine their outputs.
When to Use
- "Plan a trip to Paris Aug 11-15"
- "What's the cheapest way to do SFO to Tokyo for a week in September?"
- "How much would a trip to Stockholm cost in points vs cash?"
- Any request that involves both flights AND accommodation
When NOT to Use
- Flight-only comparison (use
compare-flights) - Hotel-only comparison (use
compare-hotels) - Award calendar (use
award-calendar) - "Should I use points?" without a specific trip (use
trip-calculator)
Workflow
Step 1: Parse Trip Parameters
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 · 196 lines · 45 tokens per session scan A 1a843b156b8f
trip-planner is a skill published in the GitHub repository borski/travel-hacking-toolkit (653 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 2,258 once invoked, about $0.0002 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 skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
using-ao
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, spawning workers, or managing AO sessions in an AO workspace.
simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.