A project rule requiring Kubernetes CRD manifests to be regenerated when the Go types that define their schemas change.

Use it after changing CRD-related Go types, validation markers, JSON fields, or API metadata by running the project's CRD generation command.

It keeps the checked-in YAML schemas synchronized with the source types so continuous integration does not fail.

crd-sync — Cursor rule for Cursor by OrlojHQ/orloj

Install

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.

Clone the repo

git clone --depth 1 https://github.com/OrlojHQ/orloj

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/orlojhq/orloj/crd-sync/github.svg)](https://agentmods.dev/rules/orlojhq/orloj/crd-sync)

Your own site

<a href="https://agentmods.dev/rules/orlojhq/orloj/crd-sync"><img src="https://agentmods.dev/badge/rules/orlojhq/orloj/crd-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/orlojhq/orloj/crd-sync"><img src="https://agentmods.dev/badge/rules/orlojhq/orloj/crd-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 422 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00422
Opus 5.5	$0.00000	$0.00169
Sonnet 5.5	$0.00000	$0.00084
Haiku 4.5	$0.00000	$0.00042

Measured 1mo ago against content hash 05e670a25212, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

crd-sync 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 1mo 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.

.cursor/rules/crd-sync.mdc · 35 lines

What it actually says

CRD manifest generation

Shared agent guidance lives in .agents/rules.md. Keep this Cursor rule consistent with that file.

When you modify Go types that feed into the Kubernetes CRD schemas, regenerate the CRD YAML so it stays in sync:

make generate-crds

This runs controller-gen (v0.21.0) and outputs to config/crd/bases/. CI will fail if the checked-in YAML doesn't match what controller-gen produces.

Files that require regeneration

crds/*_types.go — CRD struct definitions with kubebuilder markers (adding/removing fields, changing validation markers, renaming JSON tags).
resources/resource_types.go — defines AgentSystemSpec, ToolSpec, SecretSpec, AgentPolicySpec, McpServerSpec (all embedded by CRDs).
resources/agent.go — defines AgentSpec and MemorySpec (embedded by CRDs).
resources/model_endpoint.go — defines ModelEndpointSpec (embedded by CRDs).
crds/groupversion_info.go — API group/version metadata.

Files that do NOT require regeneration

crds/reconciler.go, crds/convert.go, crds/status_writer.go — runtime logic only, no schema impact.
crds/deepcopy.go — generated code (regenerated separately via controller-gen object).

After regenerating, commit the updated YAML files in config/crd/bases/ alongside your Go changes.

If the CRD schema is embedded in the Helm chart, also update charts/orloj/templates/operator-crds.yaml in the same PR.

Changes

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.

1mo ago First seen · 35 lines · 0 tokens per session scan A 05e670a25212

Subscribe to this mod's changes

crd-sync is a cursor rule published in the GitHub repository OrlojHQ/orloj (124 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 422 tokens. 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.

AI Safety Cloud DevOps and cloud agent-framework agentic-ai agentic-orchestration ai ai-governance

crd-sync

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

CRD manifest generation

What this file has done since we first saw it

Other cursor rules, from other repositories

titanclip-monorepo

titanclip-cursor-adapter

titanclip-packages

titanclip-security

titanclip-server

titanclip-ui