nvidia_gpu_exporter is a monitoring exporter that reads NVIDIA GPU measurements through the nvidia-smi program or the NVML driver library and exposes them to Prometheus. It is used to monitor GPU utilization, memory, power, and temperature on machines, containers, Kubernetes clusters, and other supported setups. The catalogue instructions cover deploying or configuring this exporter.
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 instructions/utkuozdemir/nvidia_gpu_exporter/copilot-instructionsgit clone --depth 1 https://github.com/utkuozdemir/nvidia_gpu_exporterWrote 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/instructions/utkuozdemir/nvidia_gpu_exporter/copilot-instructions)<a href="https://agentmods.dev/instructions/utkuozdemir/nvidia_gpu_exporter/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/utkuozdemir/nvidia_gpu_exporter/copilot-instructions.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.1 | $0.00341 | $0.00341 |
| Opus 5 | $0.00170 | $0.00170 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
nvidia_gpu_exporter copilot-instructions.md 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 yesterday.
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
Copilot instructions
Read AGENTS.md in the repository root first. It is the project guide, and everything below is only the short version for when you have not opened it.
- This exporter's metric names and labels are a public contract. Renaming or relabeling an established series silently breaks users' dashboards and alerts, so treat existing names as frozen.
- The expected
.metricsfiles underinternal/integration/testdata/are generated, not hand-edited. Regenerate them with the integration suite's-updateflag and review the diff. - The Helm chart's
README.mdis generated and must never be edited directly: its prose lives inREADME.md.gotmpl, and its values reference comes from the comments invalues.yaml. Regenerate with helm-docs after changing either. A new key invalues.yamlalso needs an entry invalues.schema.json, which rejects unknown keys. - The Grafana dashboards under
docs/grafana/are the source of truth; the copies shipped in the chart must stay byte-identical, and CI enforces it. Seedocs/grafana/README.mdfor the query conventions, several of which fail silently when violated. - Verify with
go test ./...and thetask lint:*target relevant to what you changed; CI runs the fulltask lintset. - Commits follow the conventional-commit format (
type(scope): imperative description) with a body explaining what changed and why, and carry a DCO sign-off. Do not add AI attribution of any kind, such as "generated with" lines or AI co-author trailers.
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.
- yesterday First seen · 11 lines · 341 tokens per session scan A 3905079de9b6
nvidia_gpu_exporter copilot-instructions.md is an instructions file published in the GitHub repository utkuozdemir/nvidia_gpu_exporter (1,550 stars, last pushed yesterday), licensed MIT. It adds 341 tokens to every session, about $0.0017 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-09-03.
Other instructions, from other repositories
netdata AGENTS.md
AGENTS.md instructions for netdata/netdata, covering agents.md, goals, requirement language, working with the user and development principles.
netdata CLAUDE.md
Claude Code instructions for netdata/netdata, a project described as: The fastest path to AI-powered full stack observability, even for lean teams.
netdata GEMINI.md
Gemini CLI instructions for netdata/netdata, a project described as: The fastest path to AI-powered full stack observability, even for lean teams.
homelab-monitor CLAUDE.md
Claude Code instructions for SikamikanikoBG/homelab-monitor, covering claude.md and conventions.
cubestat CLAUDE.md
Instructions for okuvshynov/cubestat, covering claude.md, commands, code style, architecture and collector/presenter pattern.
RuView AGENTS.md
AGENTS.md instructions for ruvnet/RuView, covering ruview repository instructions for codex, operating contract, repository map, ruview contributor harness and homecore metaharness.