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/benwilcock/rhdh-lab/copy-sync-workflowgit clone --depth 1 https://github.com/benwilcock/rhdh-labWrote 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/benwilcock/rhdh-lab/copy-sync-workflow)<a href="https://agentmods.dev/rules/benwilcock/rhdh-lab/copy-sync-workflow"><img src="https://agentmods.dev/badge/rules/benwilcock/rhdh-lab/copy-sync-workflow.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.01479 |
| Opus 5 | $0.00000 | $0.00740 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
copy-sync-workflow 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy-Sync Customization Workflow
How the System Works
rhdh-customizations/ is the single source of truth for all configuration customizations. The apply-customizations.sh script copies these files into rhdh-local/ so containers can read them from their expected mounted paths. After editing any customization file, you must re-run this script to sync.
File Mapping
Source (in rhdh-customizations/) --> Destination (copied to rhdh-local/):
compose.override.yaml-->compose.override.yaml(Compose overrides: extra services, extra_hosts).env-->.env(Environment variable overrides)configs/app-config/app-config.local.yaml-->configs/app-config/app-config.local.yaml(App config overrides)configs/dynamic-plugins/dynamic-plugins.override.yaml-->configs/dynamic-plugins/dynamic-plugins.override.yaml(Plugin overrides)configs/catalog-entities/*.override.yaml-->configs/catalog-entities/*.override.yaml(Catalog entity overrides, e.g. custom users for GitHub auth)configs/extra-files/*-->configs/extra-files/*(Additional config, e.g. github-app-credentials.yaml)
File Purposes
.env-- Environment variables (overridesrhdh-local/default.env)compose.override.yaml-- Docker Compose services, ports, volumes, extra_hostsconfigs/app-config/app-config.local.yaml-- RHDH application configurationconfigs/dynamic-plugins/dynamic-plugins.override.yaml-- Plugin enablement and configurationconfigs/extra-files/github-app-credentials.yaml-- GitHub App authentication credentials
Configuration Layers
- Layer 1 (Defaults):
rhdh-local/version-controlled files (default.env,app-config.yaml,dynamic-plugins.default.yaml) - Layer 2 (Overrides): Files copied from
rhdh-customizations/(.env,app-config.local.yaml,dynamic-plugins.override.yaml) - Layer 3 (Examples):
*.example.yamltemplates inrhdh-local/for reference
The Standard Workflow
# 1. Edit customizations (always in rhdh-customizations/)
code rhdh-customizations/configs/app-config/app-config.local.yaml
# 2. Restart (applies customizations automatically)
./lab down && ./lab up
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.
- 3d ago First seen · 137 lines · 0 tokens per session scan A 7b44109d81e9
copy-sync-workflow is a cursor rule published in the GitHub repository benwilcock/rhdh-lab (2 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,479 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-31.
Other cursor rules, from other repositories
backend
Backend development rules for TT Studio - AI model management backend.
storage-map
StorageMap controller - validation, inventory-based checks, offload plugins, mapping structure.
hack
Hack v3 is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
api-arena-no-volume-recreation
CRÍTICO — entorno de PRODUCCIÓN. Nunca recrear/borrar volúmenes Docker. Los cambios de BD se aplican SIEMPRE con migraciones idempotentes en caliente.