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/blockcell-labs/blockcell/weathernpx skills add blockcell-labs/blockcell --skill weathergit clone --depth 1 https://github.com/blockcell-labs/blockcellWrote 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/blockcell-labs/blockcell/weather)<a href="https://agentmods.dev/skills/blockcell-labs/blockcell/weather"><img src="https://agentmods.dev/badge/skills/blockcell-labs/blockcell/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.00000 | $0.00369 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 4d 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.
What it actually says
Weather
Shared {#shared}
- 适合查询城市天气、今天/明天/后天预报、是否带伞、穿衣建议。
- 默认数据源使用
wttr.inJSON：https://wttr.in/<城市>?format=j1
- 如果用户只说“明天天气怎么样”但没有城市，必须先问城市。
- 输出里要尽量使用明确日期，不要只写“今天”“明天”而不落具体日期。
Prompt {#prompt}
- 城市明确时直接执行，不要因为缺少页数、格式之类无关信息而阻塞。
- 工具策略：
- 优先调用
web_fetch获取wttr.in/<城市>?format=j1 - 当前天气读取
current_condition - 今天/明天/后天预报读取
weather[0]、weather[1]、weather[2] - 如果 JSON 缺失或不完整，再降级请求
https://wttr.in/<城市>?lang=zh
- 优先调用
- 结果整理要求：
- 先回答用户真正问的时间范围
- 再补充必要的温度、天气、降雨或风力信息
- 如果适合，补一行穿衣或带伞建议
- 建议规则：
- 温度低于 10C：提醒保暖
- 温度高于 30C：提醒防暑
- 天气描述含雨：提醒带伞
- 紫外线较高：提醒防晒
- 不要直接输出原始 JSON，不要编造未来天气。
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.
- 4d ago First seen · 29 lines · 0 tokens per session scan A f03f11eec18e
weather is a skill published in the GitHub repository blockcell-labs/blockcell (263 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 369 tokens. 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-30.
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…