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 kubiyabot/skill --skill weather-skillgit clone --depth 1 https://github.com/kubiyabot/skillWrote 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/kubiyabot/skill/weather-skill)<a href="https://agentmods.dev/skills/kubiyabot/skill/weather-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/weather-skill/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/kubiyabot/skill/weather-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/weather-skill.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.00015 | $0.00715 |
| Opus 5.5 | $0.00006 | $0.00286 |
| Sonnet 5.5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
weather scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# - Bash: Allows shell commands (curl, jq, etc.) How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weather Skill
This skill demonstrates how to build an API integration skill using the SKILL.md format.
Overview
The weather skill fetches weather data from a public API and formats it for display. It shows patterns for:
- API integration with curl
- JSON parsing with jq
- Error handling
- Optional parameters with defaults
When to Use
Use this skill when you need to:
- Check current weather for a location
- Get weather forecasts
- Integrate weather data into workflows
Tools
current
Get current weather for a city.
This tool fetches real-time weather data including temperature, conditions, and humidity.
Parameters:
city(required, string): City name (e.g., "London", "New York", "Tokyo")units(optional, string): Temperature units - "metric" for Celsius, "imperial" for Fahrenheit (default: metric)
Example:
# Basic usage
skill run weather:current city="London"
# With units
skill run weather:current city="Paris" units="metric"
skill run weather:current city="New York" units="imperial"
forecast
Get weather forecast for upcoming days.
Returns a multi-day weather forecast for the specified location.
Parameters:
city(required, string): City namedays(optional, integer): Number of days to forecast (1-5, default: 3)
Example:
# 3-day forecast (default)
skill run weather:forecast city="Berlin"
# 5-day forecast
skill run weather:forecast city="Tokyo" days=5
Implementation Notes
This skill uses:
- curl: For HTTP requests to weather API
- jq: For JSON parsing and formatting
- Environment variable:
WEATHER_API_KEYfor authentication
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 127 lines · 15 tokens per session scan A deecd6325e13
weather is a skill published in the GitHub repository kubiyabot/skill (19 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…