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/apigee/devrel/weather-lookupnpx skills add apigee/devrel --skill weather-lookupgit clone --depth 1 https://github.com/apigee/devrelWrote 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/apigee/devrel/weather-lookup)<a href="https://agentmods.dev/skills/apigee/devrel/weather-lookup"><img src="https://agentmods.dev/badge/skills/apigee/devrel/weather-lookup.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.00019 | $0.00252 |
| Opus 5 | $0.00010 | $0.00126 |
| Sonnet 5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
weather-lookup 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-lookup
Use this skill when the user asks for the weather, temperature, or forecast for a named city or region (for example, "what's the weather in Tokyo?").
This is a demonstration skill. It does not consult any live
meteorology API and ships no helper script; the agent surfaces
a canned forecast inline so the demo catalog has a second skill
to rank against apigee-policy-top10 without consuming external
quota.
When invoked, do this:
- Surface a stub response to the user in the form
weather-lookup: stub forecast -- <city>: <temperature>, <condition>using a plausible canned reading (e.g.Tokyo: 21C, partly cloudy). - Explicitly tell the user this is a demonstration skill that does
NOT consult a live meteorology provider; production use would
require wiring a real weather API and adding the corresponding
runtime_iampermissions.
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 · 33 lines · 19 tokens per session scan A 7d7e0cb9559a
weather-lookup is a skill published in the GitHub repository apigee/devrel (220 stars, last pushed 21d ago), licensed Apache-2.0. It adds 19 tokens to every session and 252 once invoked, about $0.0001 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 skills, from other repositories
implementing-api-threat-protection-with-apigee
Implement API threat protection using Google Apigee policies including JSON/XML threat protection, OAuth 2.0, SpikeArrest, and Advanced API Security for OWASP Top 10 defense.
auditing-gcp-iam-permissions
Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
datadog
Datadog monitoring integration for querying logs, metrics, monitors, events, traces, hosts, and incidents during RCA investigations.
scaleway
Scaleway cloud integration for managing instances, Kapsule Kubernetes clusters, object storage, and managed databases via CLI and Terraform.
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.