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 skills add hamzabellouch/agent-skills --skill cloud-monitoring-metric-selectiongit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/cloud-monitoring-metric-selection)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/cloud-monitoring-metric-selection"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/cloud-monitoring-metric-selection/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/skills/hamzabellouch/agent-skills/cloud-monitoring-metric-selection"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/cloud-monitoring-metric-selection.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.00078 | $0.02050 |
| Opus 5 | $0.00039 | $0.01025 |
| Sonnet 5 | $0.00016 | $0.00410 |
| Haiku 4.5 | $0.00008 | $0.00205 |
Grade B, and why
cloud-monitoring-metric-selection scanned grade B 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `~/.gemini/config/mcp_config.json` How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metric Selection (Service Query & Local Keyword Filtering)
Use this skill to identify the most relevant Google Cloud Monitoring metric descriptors. It queries all metric descriptors for a target service from the API and filters them locally inside the agent's context using keyword matching.
CRITICAL RULES
- Always Query Live APIs: You MUST always retrieve the most up-to-date
metric descriptors dynamically by calling the
list_metric_descriptorsMCP tool.
Workflow
Step 1: Verify & Auto-Configure MCP
-
Check if any tool matching
list_metric_descriptors(e.g.google-cloud-monitoring:list_metric_descriptors,mcp_google-cloud-monitoring_list_metric_descriptors, or a similar pattern) is available in your active toolset. -
Verify via Unique URL: To ensure you are calling the correct Google Cloud Monitoring tool, confirm that the underlying MCP server configuration points to:
https://monitoring.googleapis.com/mcp. -
If the tool is missing:
-
Locate the MCP configuration file for the user's environment. Check common paths:
~/.gemini/config/mcp_config.json~/.codeium/windsurf/mcp_config.jsoncline_mcp_settings.jsonclaude_desktop_config.json
-
Directly update/merge the configuration file with the following server configuration. CRITICAL: Merge the JSON object to preserve any existing MCP servers in
mcpServers. Do not overwrite the file."google-cloud-monitoring": { "url": "https://monitoring.googleapis.com/mcp", "authProviderType": "google_credentials", "enabledTools": [ "list_metric_descriptors" ] } -
Print a clear message notifying the user that the
google-cloud-monitoringMCP server has been configured, and request them to restart or start a new chat session to refresh tools. Stop calling further tools and end the turn.
-
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.
- 9d ago First seen · 200 lines · 78 tokens per session scan B 101be2cf9903
cloud-monitoring-metric-selection is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 2,050 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
opa-policies
Write OPA/Gatekeeper and Kyverno admission policies for Kubernetes security guardrails.
cost-optimization
Identify and reduce cloud infrastructure costs — right-sizing, reserved capacity, waste detection, tagging for cost attribution.
drift-detection
Detect, classify, and automate Terraform drift detection in CI — scheduled plans, drift metrics, cloud-native audit log correlation.
dns-management
DNS management for Kubernetes — CoreDNS tuning, external-dns automation, split-horizon DNS, and bare-metal DNS design.
tls-termination
Configure TLS termination with cert-manager — Let's Encrypt, internal CA via Vault PKI, wildcard certs, mTLS between services.