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 agentmods add skills/zero565656/mini-openclaw/get_weathernpx skills add zero565656/mini-openclaw --skill get_weathergit clone --depth 1 https://github.com/zero565656/mini-openclawWrote 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/zero565656/mini-openclaw/get_weather)<a href="https://agentmods.dev/skills/zero565656/mini-openclaw/get_weather"><img src="https://agentmods.dev/badge/skills/zero565656/mini-openclaw/get_weather.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 | $0.00029 | $0.00522 |
| Opus 5 | $0.00015 | $0.00261 |
| Sonnet 5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
get_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 3d 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.
resp = requests.get(url, timeout=15, verify=False) What it actually says
天气查询技能
当用户询问某个城市的天气时,使用 python_repl 工具运行以下 Python 代码来获取天气信息。
将 CITY 变量替换为用户指定的城市名(支持中文或英文城市名)。
import requests
CITY = "北京" # ← 替换为用户指定的城市名
try:
# 使用 wttr.in 的 JSON API,关闭 SSL 验证以兼容网络环境
url = f"https://wttr.in/{requests.utils.quote(CITY)}?format=j1"
resp = requests.get(url, timeout=15, verify=False)
resp.raise_for_status()
data = resp.json()
current = data["current_condition"][0]
temp_c = current["temp_C"]
feels_like = current["FeelsLikeC"]
humidity = current["humidity"]
desc = current["weatherDesc"][0]["value"]
wind_kmph = current["windspeedKmph"]
area = data["nearest_area"][0]["areaName"][0]["value"]
country = data["nearest_area"][0]["country"][0]["value"]
print(f"📍 {area}, {country}")
print(f"🌤 天气: {desc}")
print(f"🌡 温度: {temp_c}°C(体感 {feels_like}°C)")
print(f"💧 湿度: {humidity}%")
print(f"💨 风速: {wind_kmph} km/h")
except requests.exceptions.SSLError:
# SSL 失败时降级到 HTTP
try:
url = f"http://wttr.in/{requests.utils.quote(CITY)}?format=%25C+%25t+%25h+%25w"
resp = requests.get(url, timeout=15)
print(f"{CITY} 天气:{resp.text.strip()}")
except Exception as e:
print(f"天气服务不可用: {e}")
except Exception as e:
print(f"查询失败: {e}")
注意事项:
- 城市名支持中文(如"上海")或英文(如"Shanghai")
- 如果 wttr.in 完全不可用,告知用户当前网络环境无法访问天气服务
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.
- 3d ago First seen · 53 lines · 29 tokens per session scan A c18d58ba5c54
get_weather is a skill published in the GitHub repository zero565656/mini-openclaw (2 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 522 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…