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/orlojhq/orloj/crd-syncgit clone --depth 1 https://github.com/OrlojHQ/orlojWrote 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/orlojhq/orloj/crd-sync)<a href="https://agentmods.dev/rules/orlojhq/orloj/crd-sync"><img src="https://agentmods.dev/badge/rules/orlojhq/orloj/crd-sync.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 | $0.00000 | $0.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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 4d 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.
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 withkubebuildermarkers (adding/removing fields, changing validation markers, renaming JSON tags).resources/resource_types.go— definesAgentSystemSpec,ToolSpec,SecretSpec,AgentPolicySpec,McpServerSpec(all embedded by CRDs).resources/agent.go— definesAgentSpecandMemorySpec(embedded by CRDs).resources/model_endpoint.go— definesModelEndpointSpec(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 viacontroller-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.
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.
- 4d ago First seen · 35 lines · 0 tokens per session scan A 05e670a25212
crd-sync is a cursor rule published in the GitHub repository OrlojHQ/orloj (117 stars, last pushed 6d ago), 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.
Other cursor rules, from other repositories
cursorrules
When the user asks about meok watermark attest, use meok-watermark-attest-mcp tools: getdeadlinestatus, classifyobligations, generatedisclosuretext, auditcontentpipeline, signwatermarkattestation.
cursorrules
When the user asks about self healing infrastructure, use self-healing-infrastructure-mcp tools: nodehealthcheck, clusterhealthcheck, restartservice, costreport, autoremediate.
titanclip-monorepo
TitanClip pnpm monorepo layout, scripts, and scoping.
titanclip-security
Security-sensitive areas — secrets, auth, adapters, IPC.
titanclip-cursor-adapter
Cursor local adapter — CLI integration and skills sync.
titanclip-packages
Shared packages — db, shared, adapters, plugin SDK.