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 commands/openhands/extensions/nowgit clone --depth 1 https://github.com/OpenHands/extensionsWhat 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.00012 | $0.00499 |
| Opus 5 | $0.00006 | $0.00249 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
now 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 2d 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.
allowed-tools: Bash(curl:*) What it actually says
City Weather Report
Get the current time, temperature (in both Fahrenheit and Celsius), and precipitation forecast for the next 4 hours for the specified city.
Instructions
-
Parse the city name from the arguments: $ARGUMENTS
-
Use the Open-Meteo Geocoding API to find the city coordinates:
curl -s "https://geocoding-api.open-meteo.com/v1/search?name=CITY_NAME&count=1&language=en&format=json"Replace
CITY_NAMEwith the URL-encoded city name. -
Extract the latitude, longitude, and timezone from the response.
-
Use the Open-Meteo Weather API to fetch current weather and hourly forecast:
curl -s "https://api.open-meteo.com/v1/forecast?latitude=LAT&longitude=LON¤t=temperature_2m,precipitation&hourly=temperature_2m,precipitation_probability&timezone=TIMEZONE&forecast_hours=4"Replace
LAT,LON, andTIMEZONEwith the values from step 3. -
Format and present the results in a clear report:
City Weather Report for [City Name]
- Current Time: [formatted local time in the city's timezone]
- Temperature: [X]°F / [Y]°C
- Current Precipitation: [amount] mm
Precipitation Forecast (Next 4 Hours):
Time Probability [hour 1] [X]% [hour 2] [Y]% [hour 3] [Z]% [hour 4] [W]%
Example Usage
/city-weather:now New York
/city-weather:now Tokyo
/city-weather:now London
Notes
- Uses the free Open-Meteo API (no API key required)
- Temperature is provided in both Fahrenheit and Celsius
- Precipitation probability is shown for the next 4 hours
- Times are displayed in the city's local timezone
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.
- 2d ago First seen · 57 lines · 12 tokens per session scan A 4d7c05440ead
now is a command published in the GitHub repository OpenHands/extensions (137 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 499 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.