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 CodeInfinity1/Stram --skill flight-ticket-bookinggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/flight-ticket-booking)<a href="https://agentmods.dev/skills/codeinfinity1/stram/flight-ticket-booking"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/flight-ticket-booking/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/codeinfinity1/stram/flight-ticket-booking"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/flight-ticket-booking.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.00035 | $0.00838 |
| Opus 5.5 | $0.00014 | $0.00335 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
flight-ticket-booking 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flight Ticket Booking
Purpose
Find flight options, verify current fares and restrictions, compare itinerary tradeoffs, and prepare a booking review artifact. This skill supports flight booking work without executing the booking.
When To Use
Use when the user asks for flights, airfare, flight availability, flight tickets, fare classes, baggage allowances, connections, or help booking a flight.
Tool Map
web_searchresearch_web_pagesfetch_web_pagebrowser_live_statusbrowser_live_openbrowser_live_observebrowser_live_searchbrowser_live_query_selectorbrowser_live_dropdown_optionsbrowser_live_select_optionbrowser_live_clickbrowser_live_typebrowser_live_press_keybrowser_live_scrollbrowser_live_waitbrowser_live_evaluate_jsbrowser_live_screenshottravel_booking_intent_preparetravel_booking_intent_inspectpurchase_intent_preparepurchase_intent_inspectbrowser-evidence-workflowweb-form-automationsafe-shopping-and-payments
Inputs
- Origin and destination airport/city, dates, one-way/round trip/multi-city, passenger count, cabin, baggage needs, budget, and timing preferences.
- Airline/provider preference, refund/change constraints, layover tolerance, and visa/transit concerns.
- Whether the user wants current fare research, a short list, or a prepared booking intent.
Workflow
- Resolve dates concretely and state assumptions when the user gives partial or relative dates.
- Use search only for discovery when no booking/search provider URL is supplied.
- Open a concrete airline, OTA, or search provider page and verify visible route, dates, traveler count, cabin, and currency.
- Prefer source-visible fare cards over snippets. Use live browser controls for date pickers, airports, passenger counts, cabin filters, and sort/filter controls.
- For each option, capture airline/provider, flight number when visible, departure/arrival, airports, connection count, duration, cabin/fare family, fare, baggage allowance, change/refund terms, and source timestamp.
- Separate base fare from taxes, convenience fees, baggage/seat fees, and payment fees when visible.
- Do not treat fare calendars or ads as final ticket price unless the page confirms the selected itinerary and passengers.
- If the user asks to proceed, create
travel_booking_intent_preparewith flight mode, options, selected option if any, checks, uncertainties, and approval note. - Inspect the booking intent before reporting it. The status must remain
prepared_not_booked. - Stop before login, passenger data submission, seat/add-on purchase, payment, final booking, cancellation, or loyalty-account changes unless the user explicitly approved that exact action and tool policy permits it.
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 · 83 lines · 35 tokens per session scan A f88940d73f6f
flight-ticket-booking is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 838 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
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…