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-loggit 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-log)<a href="https://agentmods.dev/skills/borski/travel-hacking-toolkit/trip-log"><img src="https://agentmods.dev/badge/skills/borski/travel-hacking-toolkit/trip-log.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.00070 | $0.01149 |
| Opus 5 | $0.00035 | $0.00575 |
| Sonnet 5 | $0.00014 | $0.00230 |
| Haiku 4.5 | $0.00007 | $0.00115 |
Grade A, and why
trip-log 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trip Log Skill
Save and retrieve flight searches, award analyses, and booked itineraries from trips/logs/. Past entries are a reference library — pull them when planning connected trips, checking what was already searched, or reviewing what was booked and why.
This skill is opt-in. Create entries when the user asks ("log this trip", "save this search"), or automatically only if the user has said they want every search logged. Don't append logging to searches uninvited.
File Naming
trips/logs/YYYY-MM-DD_ORIGIN-DEST_short-label.md
YYYY-MM-DD— date the search was runORIGIN-DEST— airport codes. Multiple destinations:SFO-NRT-HND-SFOshort-label— 2–4 word slug describing the trip purpose
Examples:
trips/logs/2026-08-11_SFO-CDG_paris-anniversary.md
trips/logs/2026-07-01_JFK-NRT_japan-ana-first.md
trips/logs/2026-09-02_SFO-OSL_oslo-work-trip-booked.md
Document Structure
Every trip log file uses this structure. Sections marked required must always be present. Others only when relevant.
---
date_searched: YYYY-MM-DD # required
origin: XXX # required
destinations: [XXX, XXX] # required
travel_dates: YYYY-MM-DD to YYYY-MM-DD # required
cabin: business / premium / economy # required
status: researched # required: researched | booked | completed | cancelled
booked_option: null # fill in when booked: carrier, miles/cash, date
tags: [tag1, tag2] # freeform
points_at_search: # snapshot at search time — one key per program the user holds
example_program: 0
---
# [Trip Title]
**Searched:** YYYY-MM-DD · **Status:** Researched
**Route:** ORIGIN → DEST1 / DEST2
**Travel window:** Month DD–DD, YYYY
**Cabin:** Business class
**Travelers:** N
---
## ✅ BOOKED (fill in when booked, delete if not)
...booking details...
---
## Search Summary
One-paragraph narrative of what was searched, why, and the headline finding.
---
## Award Options (seats.aero)
Table of award results. Note whether pricing is saver or dynamic. Note data freshness.
---
## Cash Options
Table of cash prices by destination. Source each result.
---
## Points Analysis
Effective balance table (direct + transferable). CPP math for each viable award option.
Compare against points-valuations.json floors/ceilings.
---
## Recommendation
Opinionated. One clear play, one backup. Include CPP and why.
---
## Action Items
Numbered checklist of next steps (verify on airline site, transfer points, book by date, etc.)
---
## Data Notes
Sources, freshness timestamps, caveats.
*Generated by travel-hacking-toolkit · YYYY-MM-DD*
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 · 151 lines · 70 tokens per session scan A a6fc9ccfa45a
trip-log is a skill published in the GitHub repository borski/travel-hacking-toolkit (653 stars, last pushed 7d ago), licensed MIT. It adds 70 tokens to every session and 1,149 once invoked, about $0.0003 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.