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 akiotanaka847/qaio-desktop --skill plan-a-tripgit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/plan-a-trip)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/plan-a-trip"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/plan-a-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/akiotanaka847/qaio-desktop/plan-a-trip"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/plan-a-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.00060 | $0.01554 |
| Opus 5 | $0.00030 | $0.00777 |
| Sonnet 5 | $0.00012 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
plan-a-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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan A Trip
When to use
- "I'm going to {city}" / "plan my travel to {X}" / "plan a trip end-to-end".
- "flights for {conference}" / "I have a customer visit in {X}".
- "assemble my trip pack".
Connections I need
I run external work through Composio. Before this skill runs I check the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Calendar (Google Calendar, Outlook) - Required. Lets me see existing meetings during the trip window and pull events at the destination.
- Inbox (Gmail, Outlook) - Optional. Helps me find existing booking confirmations or itineraries.
- Travel providers (flight or hotel search) - Optional. If connected I surface real options; otherwise I write search criteria and you book yourself.
If no calendar is connected I stop and ask you to connect your calendar first.
Information I need
I read your operations context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- Destination and dates - Required. Why I need it: nothing works without where and when. If missing I ask: "Where are you going and on what dates? A range works if you're still flexible."
- Trip purpose - Required. Why I need it: a customer visit, a conference, an offsite, and a personal trip each get different itineraries and packing lists. If missing I ask: "What's the purpose of the trip - customer visit, conference, offsite, or personal?"
- Travel preferences - Required. Why I need it: I draft against your real preferences instead of guessing. If missing I ask: "What are your travel defaults - preferred airline, seat, hotel chain, dietary needs, anything I should always include?"
- Your timezone - Optional. Why I need it: catches schedule conflicts during the trip window. If you don't have it I keep going with TBD using your operating context default.
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.
- 7d ago First seen · 127 lines · 60 tokens per session scan A caaf54b70c47
plan-a-trip is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 1,554 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
anti-sleep
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
pipa-follow-up-reminders
Create and cancel simple one-shot email follow-up reminders through Pipa. Use this when the user wants Pipa to email them a specific reminder at a future time, such as “email me tomorrow at 9 to follow up,” “remind me by email next Friday,” or “send me a reminder in two hours.” Also use it to cancel a previously…
pipa-time-tracking
Track work time through Pipa generic agent utility records. Use when user asks to start, stop, switch, inspect, backfill, update, archive, or summarize time entries.
pipa-huddle-beta
Use when the user wants to talk through work with Pipa or their current agent in a live voice huddle: Pipa Huddle, Pipa voice session, talk this through, walking work session, plan this by voice, voice call with my agent, or discuss this out loud. Starts a voice huddle with agent context and optional handoff. Do not…
pipa-daily-shutdown
Use only when pipa-daily-shutdown is explicitly invoked or pipa-improve-operations delegates to it.
pipa
Use when the user invokes Pipa or asks to plan a service-business workday, shut down work for the day, or prepare tomorrow. Routes business operations to get work, define work, deliver work, get paid, keep clients, improve operations, Manage Pipa, or Pipa Tools.