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 mostafa-drz/claude-skills --skill weathergit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/weather)<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.
<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>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.00041 | $0.01119 |
| Opus 5 | $0.00020 | $0.00560 |
| Sonnet 5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
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 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 — 159 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 stopconfig→ interactive setup then stopreset→ 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:
- Use AskUserQuestion to ask: "Where are you located? (city name)"
- After getting weather, offer to save the location
Steps
1. Determine location
- If
$ARGUMENTScontains 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:
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 · 159 lines · 41 tokens per session scan A 6642c4ca411c
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,119 once invoked, about $0.0002 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
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
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.
ensemble-solving
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
code-execution
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
code-refactor
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
feature-planning
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.