longdo-weather

longdo-weather is a skill for Claude Code from MetamediaTechnology/longdo-skills. It costs 86 tokens per session (883 once invoked), scanned A, original, Apache-2.0.

A reference for using Longdo's weather service, an online API for Thailand's rain radar, current conditions, wind, and forecasts. It covers the shared API-key approach and common request conventions, while exact endpoints and response fields still need checking in the official documentation.

In plain words
What is it for?
Use it when adding Longdo weather data to a backend, command-line tool, mobile app, or other application.
Why use it?
It gives integration guidance without requiring you to work out the authentication and service boundaries from scratch, while flagging details that are not yet verified.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the longdo-weather plugin — 1 skill shipped together

Good fit Use it when adding Longdo weather data to a backend, command-line tool, mobile app, or other application.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/metamediatechnology/longdo-skills/longdo-weather
Install

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.

Any agent
npx skills add MetamediaTechnology/longdo-skills --skill longdo-weather
Clone the repo
git clone --depth 1 https://github.com/MetamediaTechnology/longdo-skills

Made for: Claude Code.

Or install longdo-weather, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for longdo-weather

README.md
[![agentmods](https://agentmods.dev/badge/skills/metamediatechnology/longdo-skills/longdo-weather.svg)](https://agentmods.dev/skills/metamediatechnology/longdo-skills/longdo-weather)
Your own site
<a href="https://agentmods.dev/skills/metamediatechnology/longdo-skills/longdo-weather"><img src="https://agentmods.dev/badge/skills/metamediatechnology/longdo-skills/longdo-weather.svg" alt="Measured on agentmods" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 883 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.00883
Opus 5 $0.00043 $0.00441
Sonnet 5 $0.00017 $0.00177
Haiku 4.5 $0.00009 $0.00088

Measured 8d ago against content hash f3b06ae680ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

longdo-weather 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 8d 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.

plugins/longdo-weather/skills/longdo-weather/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Longdo Weather API

Official docs: https://weather.longdo.com/docs Live service: https://weather.longdo.com/ Get a free API key: https://api.longdo.com/console/

Longdo Weather (by Metamedia Technology) provides rain radar, current conditions, wind, and forecasts for Thailand, rendered on top of the Longdo Map. It is part of the same Longdo API ecosystem as the map and location REST services.

Status of this skill: the verified, stable facts below (auth, request conventions, the service surface) are safe to rely on. The precise endpoint URLs, query parameters, and JSON response schemas live behind the JavaScript "API Docs" app at https://weather.longdo.com/docs, which can't be extracted automatically. Confirm those against the official page before shipping — see Needs verification.

Authentication

The Longdo Weather API uses the same unified Longdo API key as the map and REST services. Create / manage keys in the console: https://api.longdo.com/console/

  • Pass your key as key=YOUR_API_KEY on each request (the convention shared by all Longdo REST services).
  • Keep the key server-side. Like the location REST APIs, call weather endpoints from your backend and proxy results to clients rather than exposing the key in browser/mobile code. See the longdo-map-rest skill for the same key-handling guidance.

Shared request conventions

Longdo REST services (which the weather API follows) use:

  • GET/POST with application/x-www-form-urlencoded.
  • JSON responses by default; callback=fnName for JSONP.
  • Location via lon / lat in WGS84 degrees.
  • locale=th (default) or locale=en.

So a weather request will almost certainly take, at minimum, a location (lon/lat or a place/area identifier), your key, and an optional locale.

Rain radar on a Longdo map

Longdo Weather overlays its rain radar on a Longdo map, which means the radar is exposed as a map tile layer. In the JavaScript API (see longdo-map-js) custom raster layers are added with new longdo.Layer(name, { ... }) and map.Layers.add(...). To display the rain radar layer, get the exact layer name / tile template from the official weather docs and add it the same way you add any Longdo raster layer.

Read the full file on GitHub · 86 lines

Changes

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.

  1. 8d ago First seen · 86 lines · 86 tokens per session scan A f3b06ae680ac

Subscribe to this mod's changes

longdo-weather is a skill published in the GitHub repository MetamediaTechnology/longdo-skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 86 tokens to every session and 883 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens