claude-code-best-practice is a repository of agents, commands, skills, hooks, plugins, and configuration guidance for Claude Code. It helps developers organize repeatable workflows and apply agentic engineering practices, including in monorepos. The catalogue entries are its reusable Claude Code workflow components.
Borrowing it
Nothing to install: this file belongs to shanraisshan/claude-code-best-practice. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shanraisshan/claude-code-best-practice/main/.claude/commands/weather-orchestrator.mdgit clone --depth 1 https://github.com/shanraisshan/claude-code-best-practiceWrote 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/commands/shanraisshan/claude-code-best-practice/weather-orchestrator)<a href="https://agentmods.dev/commands/shanraisshan/claude-code-best-practice/weather-orchestrator"><img src="https://agentmods.dev/badge/commands/shanraisshan/claude-code-best-practice/weather-orchestrator/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/commands/shanraisshan/claude-code-best-practice/weather-orchestrator"><img src="https://agentmods.dev/badge/commands/shanraisshan/claude-code-best-practice/weather-orchestrator.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.00009 | $0.00452 |
| Opus 5 | $0.00005 | $0.00226 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
weather-orchestrator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- weather-orchestrator — 100% identical, 0 lines differ
What it actually says
Weather Orchestrator Command
Fetch the current temperature for Dubai, UAE and create a visual SVG weather card.
Execution Contract (non-negotiable)
You MUST complete this command by delegating to the weather-agent subagent. You are forbidden from:
- Fetching weather data yourself via Bash, WebFetch, or any other tool
- Skipping Step 1 (the user's unit preference is required input to the agent)
- Calling
weather-svg-creatorbefore the agent returns a temperature
If you cannot invoke the Agent tool, stop and report the error to the user. Do not improvise.
Workflow
Step 1: Ask User Preference
Use the AskUserQuestion tool to ask the user whether they want the temperature in Celsius or Fahrenheit. Capture the selected unit before proceeding.
Step 2: Fetch Weather Data via Agent
Use the Agent tool to invoke the weather agent:
- subagent_type: weather-agent
- description: Fetch Dubai weather data
- prompt: Fetch the current temperature for Dubai, UAE in [unit requested by user]. Return the numeric temperature value and unit. The agent has a preloaded skill (weather-fetcher) that provides the detailed instructions.
- model: haiku
Wait for the agent to complete and capture the returned temperature value and unit.
Fail-closed guardrail: If the agent does not return a numeric temperature and unit, DO NOT proceed to Step 3. Report the failure to the user and stop.
Step 3: Create SVG Weather Card
Use the Skill tool to invoke the weather-svg-creator skill:
- skill: weather-svg-creator
The skill will use the temperature value and unit from Step 2 (available in the current context) to create the SVG card and write output files.
Output Summary
Provide a clear summary to the user showing:
- Temperature unit requested
- Temperature fetched from Dubai
- SVG card created at
orchestration-workflow/weather.svg - Summary written to
orchestration-workflow/output.md
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 · 59 lines · 9 tokens per session scan A 7607d1f05d75
weather-orchestrator is a command published in the GitHub repository shanraisshan/claude-code-best-practice (65,798 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 452 once invoked, about $0.0000 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-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
version
Display current guide and Claude Code versions.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
save
Save a key-value memory entry to persistent storage.