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 618034128/Travel-Planning-Skill --skill travel-planning-skillgit clone --depth 1 https://github.com/618034128/Travel-Planning-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/skills/618034128/travel-planning-skill/travel-planning-skill)<a href="https://agentmods.dev/skills/618034128/travel-planning-skill/travel-planning-skill"><img src="https://agentmods.dev/badge/skills/618034128/travel-planning-skill/travel-planning-skill/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/618034128/travel-planning-skill/travel-planning-skill"><img src="https://agentmods.dev/badge/skills/618034128/travel-planning-skill/travel-planning-skill.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.00138 | $0.02283 |
| Opus 5 | $0.00069 | $0.01141 |
| Sonnet 5 | $0.00028 | $0.00457 |
| Haiku 4.5 | $0.00014 | $0.00228 |
Grade A, and why
travel-planning-skill 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.
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.
Travel Planning Skill
Turn a loose travel wish ("I want to go to X, leave around 9, back by 6, I really want to see Y, rest is up to you") into two deliverables:
- A route map — an interactive map if a maps/places tool is available, otherwise shareable map links.
- A time-blocked daily schedule — realistic, with travel legs, meals, and buffer time.
If the trip starts in another city, the inbound and return legs are part of the
plan too — query a real option (e.g. via a 12306 MCP) and recommend it, but never
buy the ticket yourself (see references/transport-and-booking.md).
The user can revise anything at any point ("drop that temple", "this is too rushed", "add a coffee stop"), and you regenerate only what's affected.
The one rule that defines this skill: confirm before you plan
Do not produce a route or a schedule until the user has confirmed the trip parameters. This is not bureaucracy — itinerary planning is expensive to redo, and a single wrong assumption (wrong day, wrong pace, a closed attraction) cascades through every downstream stop. Confirming first is faster overall and respects the user's time.
The user often says "everything else is up to you." That does not mean skip confirmation — it means you fill the open slots with sensible defaults and then show those defaults back for a quick yes/no. The user approves a plan-shape, not a blank check. Surface your assumptions; let them veto.
Concretely, the flow is always: Intake → Confirm → Build → Revise. Never jump from a partial request straight to a finished itinerary.
Phase 1 — Intake & Confirmation
Goal: reach a confirmed, unambiguous trip spec while asking as few questions as
possible. Read references/intake-checklist.md for the full field list, the
default values to assume, and example confirmation summaries.
Steps:
- Extract everything the user already gave. Re-read the whole conversation — they may have mentioned the city, dates, or must-sees earlier. Don't re-ask for anything already stated.
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 · 196 lines · 138 tokens per session scan A 83c921fd5fed
travel-planning-skill is a skill published in the GitHub repository 618034128/Travel-Planning-Skill (3 stars, last pushed 3mo ago), licensed MIT. It adds 138 tokens to every session and 2,283 once invoked, about $0.0007 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
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.