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 travel-and-mapsgit 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/travel-and-maps)<a href="https://agentmods.dev/skills/codeinfinity1/stram/travel-and-maps"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/travel-and-maps/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/travel-and-maps"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/travel-and-maps.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.00032 | $0.00574 |
| Opus 5.5 | $0.00013 | $0.00230 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
travel-and-maps 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Travel And Maps
Purpose
Support practical travel planning: routes, places, commute options, itineraries, venue research, and map-adjacent decisions. Current execution uses native web/browser research unless a Stram-owned maps adapter is added.
When To Use
Use for travel plans, local places, route comparisons, hotel/activity research, commute planning, timezone checks, and itinerary drafts.
Inputs And Evidence
- Origin, destination, dates, budget, mobility constraints, preferences, and region.
- Current web/map evidence, venue pages, transport pages, or user-provided notes.
- Booking, payment, or message approval state.
Tool Map
research_webpagesfetch_webpagebrowser_live_openbrowser_live_observetravel_plan_createtravel_plan_inspectwrite_notecognitive_trigger_recordmessage-approval-policy
Workflow
- Clarify location, dates, constraints, and output shape.
- Use current web evidence for changing facts such as hours, fares, closures, and weather-sensitive details.
- Compare options by time, cost, reliability, accessibility, and user preference.
- Use
travel_plan_createto preserve route options, places, itinerary days, source refs, evidence timestamps, uncertainties, and approval boundaries. - Use
travel_plan_inspectbefore reporting a saved itinerary or handing it to reminders/messages. - Stop before bookings, payments, cancellations, or messages unless approved.
Native Implementation Boundaries
- Use Stram-owned web/browser tools or future native map adapters.
- Do not import external reference map skills or external reference transportation plugins as implementation.
- Do not claim exact live routing without a current source.
travel_plan_createis a local planning artifact tool; it is not live geocoding, routing, booking, or venue contact.
Safety And Approval
- Bookings, payments, cancellations, and contacting venues require approval.
- Be careful with home/work addresses and personal travel plans.
- Mark uncertain timing and changing availability plainly.
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 · 73 lines · 32 tokens per session scan A 7122a027d168
travel-and-maps is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 574 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…