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 rules/kubev2v/forklift-console-plugin/webhooksgit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWhat 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.00021 | $0.02378 |
| Opus 5 | $0.00010 | $0.01189 |
| Sonnet 5 | $0.00004 | $0.00476 |
| Haiku 4.5 | $0.00002 | $0.00238 |
Grade A, and why
webhooks 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 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.
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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forklift API Webhooks
The forklift-api process runs Kubernetes admission webhooks over TLS on port 8443. It validates and mutates Forklift CRDs (Plans, Migrations, Providers) and their associated Secrets before they are persisted to etcd.
Source: pkg/forklift-api/ in the forklift repo.
Server Setup
pkg/forklift-api/api.go → ForkliftApi.Execute()
├── goroutine: serveServices() → :8444 (REST services, see rest-api.mdc)
└── serveWebhooks() → :8443 (admission webhooks)
- Port: 8443
- TLS: Certificates from env vars
API_TLS_CERTIFICATEandAPI_TLS_KEY - Framework: Plain
net/http.ServeMux(no gin for webhooks) - API version:
admission/v1beta1(backwards-compatible with v1)
Webhook Paths
Validating Webhooks
| Path | Handler | Resource |
|---|---|---|
/secret-validate |
SecretAdmitter |
Secret (labeled for Forklift) |
/plan-validate |
PlanAdmitter |
Plan |
/provider-validate |
ProviderAdmitter |
Provider |
/migration-validate |
MigrationAdmitter |
Migration |
Mutating Webhooks
| Path | Handler | Resource |
|---|---|---|
/secret-mutate |
SecretMutator |
Secret (labeled for Forklift) |
/plan-mutate |
PlanMutator |
Plan |
/provider-mutate |
ProviderMutator |
Provider |
Validating Webhook Details
SecretAdmitter (/secret-validate)
Dispatches by the createdForResourceType label on the Secret:
For providers secrets:
- Validates
insecurefield is a valid boolean - Rejects secrets that set both
insecure=trueand a CA certificate - Requires
createdForProviderTypelabel - On UPDATE of OVA provider secrets: rejects URL changes (OVA URLs are immutable)
- For all other provider types: builds a provider collector and runs a connection test
- 401/400 → reject with "Invalid credentials"
- Other errors → log warning but allow (connection may be temporarily unreachable)
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 · 235 lines · 21 tokens per session scan A 2eddf4e5f1ae
webhooks is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,378 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 cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.