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.
git clone --depth 1 https://github.com/gavinmcfall/home-opsWrote 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/gavinmcfall/home-ops/index)<a href="https://agentmods.dev/rules/gavinmcfall/home-ops/index"><img src="https://agentmods.dev/badge/rules/gavinmcfall/home-ops/index/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.
<a href="https://agentmods.dev/rules/gavinmcfall/home-ops/index"><img src="https://agentmods.dev/badge/rules/gavinmcfall/home-ops/index.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00600 |
| Opus 5.5 | $0.00000 | $0.00240 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
index 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Homelab Repository Context
This repository manages a Kubernetes homelab using GitOps principles with Flux, Talos, and Taskfile-driven workflows.
Core Documentation
The following files contain comprehensive context about this repository. They are the single source of truth shared across all AI coding assistants:
@docs/ai-context/README.md @docs/ai-context/ARCHITECTURE.md @docs/ai-context/DOMAIN.md @docs/ai-context/WORKFLOWS.md @docs/ai-context/TOOLS.md @docs/ai-context/CONVENTIONS.md
Quick Reference
Core Pattern
GitOps + templated manifests via Taskfile and Makejinja. Flux applies results from kubernetes/apps/*, Talos controls nodes.
Key Workflows
-
Deploy New App
- Create
kubernetes/apps/<namespace>/<app>/withkustomization.yaml,app/helmrelease.yaml,externalsecret.yaml - Run
task configure→task kubernetes:kubeconform→flux diff - Open PR, merge, monitor with
flux get helmrelease
- Create
-
Update Configuration
- Edit templates in
bootstrap/or app manifests - Run
task configureto regenerate - Validate with
task kubernetes:kubeconform - Check diff with
flux diff kustomization <namespace>
- Edit templates in
Essential Rules
- Never manually edit generated files under
kubernetes/apps/*/app/ - Always use
task configureto render templates frombootstrap/ - Use placeholders for secrets:
${SECRET_DOMAIN},${DB_URI}, etc. - Define storage explicitly in HelmRelease
persistencesections - Pin container images as
<tag>@<digest> - Follow conventional commits:
chore(app): description - Run
task kubernetes:kubeconformbefore opening PRs
Discovery Commands
# Find HelmReleases
rg --files -g"helmrelease.yaml" kubernetes/apps
# Find placeholder usage
rg -n "\${SECRET_DOMAIN}" -g"*.yaml" kubernetes/apps
# Validate manifests
task configure && task kubernetes:kubeconform
# Check Flux status
flux get kustomizations
flux diff kustomization <namespace>
File Organization
kubernetes/apps/<namespace>/<app>/- Application manifestskubernetes/flux/- Flux configurationbootstrap/- Makejinja templates (source).taskfiles/- Task modulestalosconfig/- Talos node configsscripts/- Helper scripts
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 · 77 lines · 0 tokens per session scan A 329059a10431
index is a cursor rule published in the GitHub repository gavinmcfall/home-ops (37 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 600 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-09-01.
Other cursor rules, from other repositories
working-with-operator
when the user is modifying the Kubernetes operator, CRDs, or controller logic.
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.