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 leonaero/leon_software_marketplace --skill leon-flight-searchgit clone --depth 1 https://github.com/leonaero/leon_software_marketplaceWrote 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/leonaero/leon_software_marketplace/leon-flight-search)<a href="https://agentmods.dev/skills/leonaero/leon_software_marketplace/leon-flight-search"><img src="https://agentmods.dev/badge/skills/leonaero/leon_software_marketplace/leon-flight-search/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/leonaero/leon_software_marketplace/leon-flight-search"><img src="https://agentmods.dev/badge/skills/leonaero/leon_software_marketplace/leon-flight-search.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.00191 | $0.02502 |
| Opus 5 | $0.00096 | $0.01251 |
| Sonnet 5 | $0.00038 | $0.00500 |
| Haiku 4.5 | $0.00019 | $0.00250 |
Grade A, and why
leon-flight-search 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 11d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Leon Flight Search
Purpose
Finding flights in Leon means picking from several MCP tools with overlapping-looking purposes but different filters, limits, and default behaviors. The goal here isn't to re-document their fields (the live tool schema already tells you that) — it's to get you to the right tool for the right kind of search, with the right filters resolved up front, and to flag the pagination/date- range/default-value traps that a schema alone won't warn you about.
Creating, editing, cancelling, restoring, or tagging flights and trips is out of scope here — see
leon-trip-manager for that. Passenger lists, Journey Log content, permits, fuel prices, and
crew assignment are also out of scope — each has its own specialized tooling; this skill only
finds and identifies flights, not the data attached to them beyond core schedule/aircraft facts.
Which tool for which job
| You want to... | Use |
|---|---|
| Find flights by date range, route, aircraft, crew, status, cancellation, ferry flag, tags, or country | search-flights |
| Find all flights on a trip you already have the number for | search-trips-by-trip-number → get-trips-by-trip-nids |
| Get full detail (aircraft, times, actual Journey Log data) for flight(s) you already have the NID for | get-flights-by-flight-nids |
| Check whether there's ever been (or is scheduled to be) a flight from a given airport | find-last-flight-from |
| Check whether there's ever been (or is scheduled to be) a flight to a given airport | find-last-flight-to |
| See which flights were created, changed, or deleted recently | get-modified-flight-nid-list |
| See which flights' Journey Logs were created, changed, or deleted recently | get-modified-journey-log-nid-list |
When search-flights' filters aren't enough (custom column combos, unsupported filter) |
get-report-wizard-flight-scope-columns-list → get-report-wizard-flight-scope-report |
| Resolve an airport by name/city, fuzzy | search-airports-by-wildcard |
| Resolve an airport by exact code | get-airport-by-code |
| Resolve an aircraft registration to a NID | get-aircraft-by-registration |
| Resolve a tag by name | search-flight-tags-by-name |
| Resolve a crew member to a NID | search-contacts-by-wildcard / get-flights-crew |
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.
- 11d ago First seen · 166 lines · 191 tokens per session scan A 45e5d296cb50
leon-flight-search is a skill published in the GitHub repository leonaero/leon_software_marketplace (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 191 tokens to every session and 2,502 once invoked, about $0.0010 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…