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 mostafa-drz/claude-skills --skill make-it-itinerarygit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/make-it-itinerary)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/make-it-itinerary"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/make-it-itinerary/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/mostafa-drz/claude-skills/make-it-itinerary"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/make-it-itinerary.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.00185 | $0.02754 |
| Opus 5.5 | $0.00074 | $0.01102 |
| Sonnet 5.5 | $0.00037 | $0.00551 |
| Haiku 4.5 | $0.00018 | $0.00275 |
Grade A, and why
make-it-itinerary 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 28d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make it an itinerary
You've been chatting about a trip: a place, where to stay, where to eat. This turns that conversation into a plan you can actually travel with. It keeps what you decided, asks only what it can't work out, checks every stop against the real dates, and hands you a page that works on your phone, on paper, and in your calendar.
The very important point is user-centric design and workflow thinking, and grounding every suggestion in online verification, based on the current date. (from the original sketch)
In Claude Desktop and claude.ai the skill starts automatically on a matching request, with no slash command. Typing "make it an itinerary" is the natural trigger.
Four references, loaded when a step needs them:
trip-brief.md (reading the conversation and asking the
right questions) · verification.md (grounding each
suggestion online) · itinerary-schema.md (the data
every output renders from) · examples.md (the full journeys:
thin chat, rich chat, edits, no web search).
The flow
conversation → fill the gaps → travel itinerary. Copy this checklist into your reply
and tick it off as you go, because skipping step 4 or 5 is how a confident-looking plan
ends up wrong on the day:
Itinerary progress:
- [ ] 1. Harvest the conversation (committed, liked, rejected, floated)
- [ ] 2. Fill the gaps: one round, ≤3 questions, defaults offered
- [ ] 3. Draft the days
- [ ] 4. Verify each item for the trip dates
- [ ] 5. Validate itinerary.json
- [ ] 6. Render and deliver
1. Harvest
Read the whole conversation before asking anything. Sort what's there into
committed (kept exactly), liked (included), rejected (never brought back) and
floated (candidates only). Earlier replies weren't verified. Being in the chat isn't
proof. Detail and edge cases are in trip-brief.md.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/itinerary-template.html 19 KB
- evals/evals.json 3.1 KB
- icon.svg 752 B
- README.md 7.7 KB
- references/examples.md 5.5 KB
- references/itinerary-schema.md 7.6 KB
- references/trip-brief.md 6.3 KB
- references/verification.md 6.8 KB
- scripts/make_ics.py 7.0 KB runs code
- scripts/render_page.py 1.7 KB runs code
- scripts/validate_itinerary.py 17 KB runs code
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.
- 28d ago First seen · 228 lines · 185 tokens per session scan A e1f73ea72092
make-it-itinerary is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 20d ago), licensed MIT. It adds 185 tokens to every session and 2,754 once invoked, about $0.0007 per session on Opus 5.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-09-23.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.