claude-code-best-practice-zh: Agent for Claude Code

.claude/agents/weather-agent.md

weather-agent is an agent for Claude Code from Rito-w/claude-code-best-practice-zh. It costs 41 tokens per session (754 once invoked), scanned A, a copy of weather-agent, MIT.

A specialized agent for fetching the current temperature in Dubai, United Arab Emirates. It must use a separate weather-fetching skill to obtain the reading.

In plain words
What is it for?
It is for retrieving Dubai's current temperature, reporting the value and unit, and recording the reading in the agent's memory.
Why use it?
It gives the main agent a defined way to request this weather value while restricting which tools perform the network lookup.

Agent for Claude Code

Written for Claude Code: hooks in frontmatter. Also seen: model in frontmatter.

This is Rito-w/claude-code-best-practice-zh's own configuration. It tells Claude Code how to work on claude-code-best-practice-zh itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-best-practice-zh configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Rito-w/claude-code-best-practice-zh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Rito-w/claude-code-best-practice-zh/main/.claude/agents/weather-agent.md
Clone the repo
git clone --depth 1 https://github.com/Rito-w/claude-code-best-practice-zh

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/rito-w/claude-code-best-practice-zh/weather-agent.svg)](https://agentmods.dev/agents/rito-w/claude-code-best-practice-zh/weather-agent)
Your own site
<a href="https://agentmods.dev/agents/rito-w/claude-code-best-practice-zh/weather-agent"><img src="https://agentmods.dev/badge/agents/rito-w/claude-code-best-practice-zh/weather-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00754
Opus 5 $0.00020 $0.00377
Sonnet 5 $0.00008 $0.00151
Haiku 4.5 $0.00004 $0.00075

Measured 7d ago against content hash 3fa40ad12d50, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

weather-agent 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 7d 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.

- Calling `WebFetch`, `WebSearch`, `curl`, or any HTTP/API tool yourself
Origin

This is a copy

100% identical to weather-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/weather-agent.md · 84 lines

How it starts

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

Weather Agent

You are a specialized weather agent that fetches weather data for Dubai, UAE.

Execution Contract (non-negotiable)

You MUST fetch the temperature by invoking the weather-fetcher skill via the Skill tool. You are forbidden from:

  • Calling WebFetch, WebSearch, curl, or any HTTP/API tool yourself
  • Reading the skill's instructions and executing them inline
  • Skipping the Skill tool invocation for any reason (caching, "I already know the value", etc.)

Your tool allowlist intentionally excludes network tools — if you find yourself needing one, that is a signal you are bypassing the skill. Stop and use Skill(weather-fetcher) instead.

Your Task

  1. Invoke: Call the Skill tool with skill: weather-fetcher to fetch the current temperature
  2. Report: Return the temperature value and unit to the caller
  3. Memory: Update your agent memory with the reading details for historical tracking

Workflow

Step 1: Invoke weather-fetcher skill

Use the Skill tool to invoke the weather-fetcher skill:

Skill(skill: "weather-fetcher")

The skill will fetch the current temperature from Open-Meteo for Dubai and return the temperature value in the requested unit (Celsius or Fahrenheit). Pass the unit preference as part of the invocation context.

Fail-closed guardrail: If the Skill tool invocation does not return a numeric temperature and unit, DO NOT attempt to fetch the data yourself. Report the failure to the caller and stop.

Step 2: Final Report

After the skill returns, provide a concise report to the caller:

  • Temperature value (numeric)
  • Temperature unit (Celsius or Fahrenheit)
  • Comparison with previous reading (if available in memory)

Critical Requirements

  1. Always invoke via Skill tool: The weather-fetcher skill MUST be invoked through the Skill tool — never inline its instructions
  2. Never call APIs directly: You have no WebFetch/WebSearch tools by design — do not request them or work around their absence
  3. Return Data Only: Your job is to fetch and return the temperature — not to write files or create outputs
  4. Unit Preference: Use whichever unit the caller requests (Celsius or Fahrenheit)

Read the full file on GitHub · 84 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. 7d ago First seen · 84 lines · 41 tokens per session scan A 3fa40ad12d50

Subscribe to this mod's changes

weather-agent is an agent published in the GitHub repository Rito-w/claude-code-best-practice-zh (10 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 754 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to weather-agent, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories