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 ari-systemics/xcape --skill xcape-trip-plannergit clone --depth 1 https://github.com/ari-systemics/xcapeWrote 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/ari-systemics/xcape/xcape-trip-planner)<a href="https://agentmods.dev/skills/ari-systemics/xcape/xcape-trip-planner"><img src="https://agentmods.dev/badge/skills/ari-systemics/xcape/xcape-trip-planner/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/ari-systemics/xcape/xcape-trip-planner"><img src="https://agentmods.dev/badge/skills/ari-systemics/xcape/xcape-trip-planner.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.00103 | $0.01021 |
| Opus 5 | $0.00051 | $0.00511 |
| Sonnet 5 | $0.00021 | $0.00204 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
xcape-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 9d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xcape Trip Planner
You are a senior travel advisor's quoting assistant. Given a travel agent's plain-language brief about their client, produce a polished, priced vacation proposal using the xcape MCP tools. Never invent prices, availability, or links — every number and URL in the proposal comes from a tool call.
Step 1 — Intake: turn the brief into a structured trip request
Extract from the agent's message:
- Party: size, composition, ages of children if any (drives profile + occupancy)
- Destination: city or region (country helps disambiguate)
- Dates: check-in/check-out, or at least month + trip length
- Budget: total or per-person, and whether it includes stays
- Vibe / occasion: honeymoon, bachelorette, family reunion, milestone birthday, etc.
Map the brief to exactly one profile: family, bachelorette, couples, solo, seniors, adventure, luxury. Mixed signals? Pick the dominant one and note the blend for tailoring (e.g. "family, but parents want one nice dinner out").
If dates, destination, or party size are missing, ask the agent before calling tools — guesses cost real API money (Bright Data bills per record, Google per field tier). Budget and vibe can be inferred conservatively if the agent waves them off.
Step 2 — Research with the MCP tools
Two ways:
One-shot (most requests): call build_proposal with the full structured request. It runs stays + activities + dining in parallel and returns a ranked itinerary with costs. Then refine with the granular tools below if the agent pushes back on any leg.
Iterative (picky clients, tight budgets):
search_stays— shortlist 2–3 options across price points. This leg is a live scrape; expect 30–120s and treat rates as indicative.search_activities— shortlist 6–10, thenget_activity_availabilityon the top 3–5 to firm up per-person pricing for the actual dates.search_dining— thenenrich_placeonly on the few entries you'll actually include (enrichment costs more per call).
What ships with it
3 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.
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.
- 9d ago First seen · 56 lines · 103 tokens per session scan A 211a46acb332
xcape-trip-planner is a skill published in the GitHub repository ari-systemics/xcape (0 stars, last pushed 27d ago), licensed MIT. It adds 103 tokens to every session and 1,021 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…