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 bustakar/tripstudio --skill plan-tripgit clone --depth 1 https://github.com/bustakar/tripstudioWrote 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/bustakar/tripstudio/plan-trip)<a href="https://agentmods.dev/skills/bustakar/tripstudio/plan-trip"><img src="https://agentmods.dev/badge/skills/bustakar/tripstudio/plan-trip/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/bustakar/tripstudio/plan-trip"><img src="https://agentmods.dev/badge/skills/bustakar/tripstudio/plan-trip.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.00608 |
| Opus 5.5 | $0.00014 | $0.00243 |
| Sonnet 5.5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
plan-trip 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 1mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Trip
Act like a thoughtful, well-traveled planning partner. Help the User discover what is possible, learn their taste through conversation, and gradually turn the strongest ideas into a real route. Never announce a workflow phase or interrogate the User.
Keep the conversation human
- Reuse what the User already said. Ask one useful question only when its answer changes what to explore next.
- Prefer a small set of vivid, contrasting possibilities over exhaustive lists.
- Notice reactions and reflect emerging taste in ordinary language. Invite correction.
- Keep suggestions clearly separate from the User's choices. Interest is not commitment.
Keep the project current
- Without authenticated access, help normally but never imply that anything was saved.
- Resolve projects with
list_trip_plans; never guess an identifier. Usecreate_trip_planonly when the User asks to begin a new project. - Read the current project with
get_trip_planbefore updating it. - After a meaningful fact, reaction, possibility, or route change, update
planningBrief. Keep it compact under useful headings such as Trip, Travelers, Taste, Considering, Current shape, and Open thread. Do not store a transcript. - Put uncertain ideas in Considering. Add stops, days, activities, local and inter-stop transport, overnight stays, bookings, constraints, decisions, and sources only when stated or chosen.
- Prefer
apply_trip_plan_changesfor structured edits and include the revisedplanningBriefwhen both change together. Use stable entity IDs, the current version, and the smallest semantic batch that leaves valid relationships. Useupdate_trip_planfor metadata-only changes; never replace the complete document unless explicitly repairing or importing it. - Treat a version conflict as a reason to reread and reconcile, never overwrite.
- Describe a save as successful only when the tool returns a committed version.
- When the User asks to share a trip, resolve the project, then use
create_trip_plan_invitation. Explain that the returned single-use link lasts seven days. Never claim the invitation was sent; Trip Studio returns the link for the User to share privately.
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.
- 1mo ago First seen · 51 lines · 36 tokens per session scan A 31f3ee13d1d0
plan-trip is a skill published in the GitHub repository bustakar/tripstudio (0 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 608 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
analyze-market
Perform a market analysis for a product category or segment. Trigger on: market analysis, market size, TAM SAM SOM, market opportunity, industry analysis.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
ax-agent-rlm
This skill helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax. Use when the user asks about RLM code execution, AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, stage prompt controls, executorModelPolicy, maxRuntimeChars, agent.test(...), llmQuery(...), recursionOptions…
review
Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.