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/hook-controllergit 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.00015 | $0.01136 |
| Opus 5 | $0.00008 | $0.00568 |
| Sonnet 5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
hook-controller 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Controller
Source: pkg/controller/hook/ (validation), pkg/controller/plan/hook.go (execution)
Two Concerns
The Hook lifecycle is split across two controllers:
- Hook controller (
pkg/controller/hook/) — validates the Hook CRD and sets Ready. - Plan controller (
pkg/controller/plan/hook.go) — executes hooks viaHookRunnerduring migration phasesPreHookandPostHook.
Hook CRD Validation
Reconciliation Flow
Fetch Hook CR
→ BeginStagingConditions
→ validate()
→ If spec.aap is set:
→ Reject if image or playbook also set (InvalidHookExecute)
→ validateAAP() — url, jobTemplateId > 0, tokenSecret.name required
→ If spec.aap is nil (local hook):
→ HookExecutionConfigValid() — image is required, playbook optional
→ validateImage() — Docker image reference regex (OCI-compliant)
→ validatePlaybook() — must be valid base64 if provided
→ Set Ready if no blockers
→ EndStagingConditions, record events, update status
Conditions
| Condition | Category | When Set |
|---|---|---|
InvalidImage |
Critical | Image name fails OCI reference regex |
InvalidPlaybook |
Critical | Playbook is not valid base64 |
InvalidHookExecute |
Critical | Invalid combination: AAP + image/playbook, or missing image for local hook |
Ready |
Required | No blocker conditions |
Image Validation
The regexp.go file contains a full OCI/Docker image reference parser:
- Validates
[domain/]name[:tag][@digest]format. - Supports multi-level paths, port numbers, tags, and SHA digests.
Hook Execution (HookRunner)
File: pkg/controller/plan/hook.go
Invoked by the migration controller during PhasePreHook and PhasePostHook:
runner := HookRunner{Context: r.Context}
err = runner.Run(vm)
Two Execution Modes
1. Local Hook (Kubernetes Job)
When spec.aap is nil:
- ConfigMap: Created with
workload.yml(VM inventory data),playbook.yml(decoded from base64), andplan.yml(plan spec as YAML). - Job: Created in the plan's namespace with:
- Container image from
hook.Spec.Image - ConfigMap mounted at
/tmp/hook - If playbook provided: command is
/bin/entrypoint ansible-runner run /tmp/runner -p /tmp/hook/playbook.yml BackoffLimit: 1- Resource requests/limits from
Settings.Migration.HooksContainer{Requests,Limits}{Cpu,Memory} ActiveDeadlineSecondsfromhook.Spec.Deadline(if > 0)
- Container image from
- Service account precedence: Hook SA → Plan SA → Global controller SA → namespace default.
- Owned by Plan: Job has owner reference to the Plan CR.
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 · 118 lines · 15 tokens per session scan A 180b59d97342
hook-controller 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 15 tokens to every session and 1,136 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.