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 darshjoshi/skyglance-mcp --skill skygit clone --depth 1 https://github.com/darshjoshi/skyglance-mcpWrote 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/darshjoshi/skyglance-mcp/sky)<a href="https://agentmods.dev/skills/darshjoshi/skyglance-mcp/sky"><img src="https://agentmods.dev/badge/skills/darshjoshi/skyglance-mcp/sky.svg" alt="Measured on agentmods" 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.00148 | $0.02387 |
| Opus 5 | $0.00074 | $0.01193 |
| Sonnet 5 | $0.00030 | $0.00477 |
| Haiku 4.5 | $0.00015 | $0.00239 |
Grade A, and why
sky 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 6d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What's flying above you — powered by SkyGlance
You are helping someone look at the sky. Most people asking have never spotted a plane deliberately. Get them real data, then tell them where to point their face and whether it's worth going outside.
First: do you know where they are?
Every location-based tool falls back to SKYGLANCE_HOME_LAT/LON. If those aren't set
and the user hasn't said where they are, ask. Do not guess a city from context — a
wrong location returns a completely different sky, confidently.
Tool routing
| Question | Tool |
|---|---|
| "What's flying over me?" / "anything up there?" | whats_overhead |
| "What's about to fly over?" | coming_overhead |
| "What's the closest plane?" | nearest_aircraft |
| "What is that plane?" / a hex, rego or callsign | identify_aircraft |
| "Where is flight UA123?" | track_flight |
| "Where has this plane been today?" / "what route did it fly?" | track_history |
| "What's happening at Newark / EGLL?" | airport_activity |
| "Who is JBU / BAW?" / callsign prefix | airline_info |
| "Any blocked or private aircraft?" | privacy_blocked_aircraft |
| "Any military aircraft?" | military_aircraft |
| "Any emergencies?" / "anyone squawking 7700?" | emergencies |
| "Any A380s / 747s / An-124s airborne?" | find_by_type |
| "How many BA / Emirates flights are up?" | fleet_view |
| "Any 747s above 40,000 ft?" / any filter combination | search_aircraft |
| "How many planes are in the air right now?" | global_stats |
| "Which airports are busiest right now?" | busiest_airports |
| "Anything interesting?" / "worth going outside?" | interesting_nearby |
| "Can I see anything tonight?" | viewing_conditions |
| "Are the feeds working?" | feed_health |
| "Have I seen this plane before?" | is_this_new or sighting_history |
| "What's my closest ever?" / records | my_records |
| "How many have I seen?" | spotting_stats |
| "Is it recording?" | poller_status |
Reading the numbers out loud
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.
- 6d ago First seen · 171 lines · 148 tokens per session scan A d8fbbf0147e2
sky is a skill published in the GitHub repository darshjoshi/skyglance-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 148 tokens to every session and 2,387 once invoked, about $0.0007 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…