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.
git clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWrote 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/rules/kubev2v/forklift-console-plugin/monitoring)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/monitoring"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/monitoring/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/rules/kubev2v/forklift-console-plugin/monitoring"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/monitoring.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.00013 | $0.02405 |
| Opus 5.5 | $0.00005 | $0.00962 |
| Sonnet 5.5 | $0.00003 | $0.00481 |
| Haiku 4.5 | $0.00001 | $0.00241 |
Grade A, and why
monitoring 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 29d 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring & Metrics
Analyzed from commit:
baf9c7bcc307ed9358ad59886a5536366a050012on 2026-09-17 Source paths:pkg/monitoring/,pkg/metrics/
Package Purpose
Forklift exposes mtv_* Prometheus metrics for migration/plan lifecycle observability
and vSphere XCOPY copy-offload performance. Metric definitions and recording loops live
in pkg/monitoring/metrics/forklift-controller/. The HTTP serving layer is split between
the controller binary (cmd/forklift-controller/main.go) and a reusable TLS helper
(pkg/metrics/promethousutil.go) used by volume populators.
Prometheus Endpoint
forklift-controller (production path)
cmd/forklift-controller/main.go
├── promhttp.Handler() on :2112/metrics (plain HTTP, default registry)
└── controller-runtime --metrics-bind-address=127.0.0.1:8080/metrics
operator/config/default/manager_auth_proxy_patch.yaml
└── kube-rbac-proxy :8443 → upstream :8080 (TLS + RBAC for Prometheus)
operator/config/prometheus/monitor.yaml
└── ServiceMonitor scrapes :8443/metrics (scheme: https)
promauto.New* registers mtv_* metrics with prometheus.DefaultRegisterer, served by
promhttp.Handler() on :2112. Controller-runtime v0.20.4 serves its separate
metrics.Registry on :8080; the ServiceMonitor path (:8443 via kube-rbac-proxy) scrapes
controller-runtime metrics only — mtv_* metrics are not exposed there unless explicitly
registered with the controller-runtime registry.
Volume populators (sidecar jobs)
pkg/metrics/promethousutil.go → StartPrometheusEndpoint(certsDirectory):
- Generates self-signed TLS cert/key at startup
- Serves
/metricsover HTTPS on port 8443 - Used by
cmd/ovirt-populator/andcmd/openstack-populator/
Note: upstream filename is
promethousutil.go(typo preserved).
Key Types and Structs
All metrics are package-level var blocks in
pkg/monitoring/metrics/forklift-controller/metrics.go, registered via promauto
(no manual prometheus.Register for controller metrics).
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.
- 29d ago Changed · +136 lines 18499c7fbd08
- 1mo ago First seen · 89 lines · 13 tokens per session scan A c822113d65a1
monitoring is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 2,405 once invoked, about $0.0001 per session on Opus 5.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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.