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 AtlasOmnia/hermes-custom-pack --skill destination-trip-planninggit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packWrote 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/atlasomnia/hermes-custom-pack/destination-trip-planning)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/destination-trip-planning"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/destination-trip-planning/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/atlasomnia/hermes-custom-pack/destination-trip-planning"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/destination-trip-planning.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.00036 | $0.02089 |
| Opus 5 | $0.00018 | $0.01045 |
| Sonnet 5 | $0.00007 | $0.00418 |
| Haiku 4.5 | $0.00004 | $0.00209 |
Grade A, and why
destination-trip-planning scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Travel/attraction websites frequently block web_extract and even browser_navigate.** They use Cloudflare or JS-heavy rendering. Fallback chain: search-result snippets → press releases on the official site → third-par This is a copy
100% identical to destination-trip-planning — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Destination Trip Planning
Plan themed trips to specific attractions or destinations with real pricing, logistics, and a tight itinerary focused on the theme — not a generic city guide.
When to Use
- User wants to plan a trip to a specific attraction, event, or themed destination (e.g., Graceland, a national park, a festival, a resort)
- User asks for "what to do there" at a given destination
- User needs a go/no-go recommendation on trip length and budget
- User wants to know what's nearby that fits the same theme
Core Workflow
Phase 1: Lock the Destination and Constraints
Clarify up front:
- Exact destination — confirm the city/location (Graceland = Memphis, not Nashville)
- Traveler profile — age, mobility, energy level, interests
- Time window — exact check-in and checkout dates, calendar days, and number of nights; if the user corrects the duration, recompute the entire budget
- Traveler and payment structure — total headcount, ages, likely activity participants, and which person/team pays which share
- Budget sense — looking for deals vs. full-service package
- 2–3 day trip vs longer
Phase 1.5: Clarify What "The Attraction" Actually Is
First-time visitors often don't know the attraction's layout. Preempt "is it just a house?" or "the house is the museum, right?" moments by describing the physical campus up front:
- Is the attraction one building or a campus spread across multiple sites?
- What's the ticket actually cover? (e.g., Graceland's $85 Elvis Experience = mansion across the street + 200K sq ft exhibit complex + two airplanes + on-site dining/shopping)
- Are there free areas (gravesite, gates, grounds)?
- Can the traveler see everything without re-entering or is it split across days?
This matters more for older travelers — they need to know if there's significant walking, shuttles, or stairs between components.
Phase 2: Gather Destination Research
For the primary attraction:
- Ticket pricing tiers (standard vs VIP vs all-access)
- How long the full experience takes
- Peak vs off-peak times
- Available discounts (senior, AAA, military, promo codes)
- Parking / shuttle / accessibility info
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 · 162 lines · 36 tokens per session scan A af77b9563441
destination-trip-planning is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (56 stars, last pushed 28d ago), licensed MIT. It adds 36 tokens to every session and 2,089 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to destination-trip-planning, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
config
Use when configuring obshare-cli credentials, checking saved settings, testing connectivity, clearing local config, or setting optional Obsidian bridge values used by the V0.2.0 direct-share stack.
obshare-cli
Use when setting up obshare-cli 0.2.0, reviewing available commands, or choosing the right command for config, upload, permission, history, delete, and the plugin-first direct-share workflow.
agent-dreaming-agnostic
Memory-agnostic background consolidation — reviews sessions, scores candidates, promotes durable insights to the active memory backend (built-in MEMORY.md or Holographic). Three-phase (Light/Deep/Condensation/REM). Run via cron or manually.
upload
Use when uploading a Markdown note to Feishu, optionally applying public or copy/download permissions, or requesting JSON upload results for automation or the Obsidian plugin direct-share flow.
permission
Use when changing Feishu document visibility, copy permissions, or download permissions for an uploaded document token.
list
Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.