weather

weather is a skill for Claude Code from mostafa-drz/claude-skills. It costs 41 tokens per session (1,137 once invoked), scanned A, original, MIT.

A skill for checking current weather with live online data, using either a saved location or a city supplied for one request.

In plain words
What is it for?
Use it to see current conditions or a forecast, set or change the saved city, and clear the saved location.
Why use it?
It avoids relying on outdated weather information and can remember a default location for future checks.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Good fit Use it to see current conditions or a forecast, set or change the saved city, and clear the saved location.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mostafa-drz/claude-skills/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 mostafa-drz/claude-skills --skill weather
Clone the repo
git clone --depth 1 https://github.com/mostafa-drz/claude-skills

Made for: Claude Code.

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 weather

README.md
[![agentmods](https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/weather/github.svg)](https://agentmods.dev/skills/mostafa-drz/claude-skills/weather)
Your own site
<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/weather"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/weather/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.

agentmods 80×15 button for weather

Your own site · 80×15
<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/weather"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/weather.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,137 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.00041 $0.01137
Opus 5.5 $0.00016 $0.00455
Sonnet 5.5 $0.00008 $0.00227
Haiku 4.5 $0.00004 $0.00114

Measured 1mo ago against content hash 45667add8aea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

code/weather/SKILL.md · 161 lines

How it starts

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

Weather

Check the current weather for your location using live data from Open-Meteo (free, no API key needed).

Preferences

Read ~/.claude/skills/weather/preferences.md using the Read tool. If not found, no preferences are set.

Command routing

Check $ARGUMENTS:

  • help → display help then stop
  • config → interactive setup then stop
  • reset → delete ~/.claude/skills/weather/preferences.md, confirm, stop
  • anything else (including empty) → run the skill

Help

Weather — Check current weather for your location

Usage:
  /weather                     Show weather for saved location
  /weather Berlin              Show weather for Berlin
  /weather config              Set your default location
  /weather reset               Clear saved location
  /weather help                This help

Examples:
  /weather                     Uses your saved city
  /weather "New York"          One-off check for New York
  /weather Tokyo               One-off check for Tokyo

Current preferences:
  (shown above under Preferences)

Config

Use AskUserQuestion:

Q1 — "What city are you in?" (text input via Other)

  • Options: suggest common cities as quick picks, plus Other for custom input

Q2 — "Temperature unit?"

  • Celsius (default)
  • Fahrenheit

Save to ~/.claude/skills/weather/preferences.md.

Reset

Delete ~/.claude/skills/weather/preferences.md and confirm: "Preferences cleared. Using defaults."

First-time detection

If no preferences file exists and no city argument was provided:

  1. Use AskUserQuestion to ask: "Where are you located? (city name)"
  2. After getting weather, offer to save the location

Steps

1. Determine location

  • If $ARGUMENTS contains a city name (not help/config/reset) → use that city
  • Else if preferences has a saved city → use that
  • Else → ask via AskUserQuestion: "What city should I check the weather for?"

2. Geocode the city

Use WebFetch to call the Open-Meteo geocoding API:

Read the full file on GitHub · 161 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. 1mo ago Changed · +2 lines 45667add8aea
  2. 1mo ago First seen · 159 lines · 41 tokens per session scan A 6642c4ca411c

Subscribe to this mod's changes

weather is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,137 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

rudder-data-graphs

Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.

rudderlabs/rudder-agent-skills · 40 tokens

rudder-typer-workflow

Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.

rudderlabs/rudder-agent-skills · 43 tokens

rudder-instrumentation-planning

Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.

rudderlabs/rudder-agent-skills · 32 tokens

rudder-instrumentation-debugging

Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.

rudderlabs/rudder-agent-skills · 34 tokens

rudder-ai-events-verify

Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.

rudderlabs/rudder-agent-skills · 66 tokens