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 instructions/edgard/home-ops/agents-mdgit clone --depth 1 https://github.com/edgard/home-opsWhat 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.02581 | $0.02581 |
| Opus 5 | $0.01290 | $0.01290 |
| Sonnet 5 | $0.00516 | $0.00516 |
| Haiku 4.5 | $0.00258 | $0.00258 |
Grade B, and why
home-ops AGENTS.md scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- s6-overlay: run as root + SETUID/SETGID; ports <1024: +NET_BIND_SERVICE How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Ops
GitOps Talos Kubernetes homelab (single-node, local-only). Changes via PR only. Tech: Talos • K8s • Argo CD • Istio Gateway API • External Secrets (Bitwarden) • VictoriaMetrics/VictoriaLogs/VLAgent/Grafana • Helm • Ansible • Terraform
Build & Test
- Format:
task fmt - Format check:
task fmt:check - Dependencies:
task depscreates.venvand installs Ansible Python dependencies - Lint:
task lint(offline validation: formatting, shellcheck, yamllint, GitHub Actions workflow lint, Ansible syntax/lint/contracts, metadata policy, raw manifest policy/schema/deprecation checks, batched rendered policy/schema/deprecation checks,tofu validate) - Focused checks:
task lint:static,task lint:workflows,task lint:ansible,task lint:kubernetes,task lint:terraform - Policy layers:
policy/metadata/validates app metadata structure and required sync wavespolicy/kubernetes/validates manifest and rendered-workload guardrails
- Policy semantics are regression-tested in
policy/metadata/*_test.regoandpolicy/kubernetes/*_test.rego - CI gate: GitHub
Quality Gatejob, backed by the same focused localtask lint:*targets aggregated bytask lint - Pre-commit gate:
task precommit(task fmt+task lint) - Sync ArgoCD app:
task argo:sync [app=<name>](GitOps: changes must be committed and pushed to repo first)
Developer Loop
- Make a small change
- If behavior changes, write or update the failing policy or contract check first
- Use
task lintwhile iterating when changing script behavior or Helm/app compatibility - Run
task fmt - Run
task lintbefore commit or PR update
Project Layout
apps/<category>/<app>/{app.yaml,values.yaml,manifests/}
argocd/appsets/ # Auto-discovers apps/*/*/app.yaml
ansible/ # Local orchestration, inventory, roles, role defaults, and Talos bootstrap inputs
terraform/ # Cloudflare/Tailscale infra
App Categories:
- platform-system: cert-manager, external-dns, external-secrets, gateway-api, istio, istio-base, prometheus-blackbox-exporter, reloader, tailscale-router, victoria-logs-collector, victoria-logs-single, victoria-metrics-k8s-stack
- kube-system: coredns, k8s-gateway, k8tz, multus, nfs-provisioner
- home-automation: homeassistant, scrypted
- media: bazarr, flaresolverr, plex, plextraktsync, prowlarr, qbittorrent, radarr, recyclarr, sonarr, unpackerr
- selfhosted: atuin, changedetection, echo, karakeep, paperless, renovate-operator, restic
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 · 192 lines · 2,581 tokens per session scan B fd9848db6413
home-ops AGENTS.md is an instructions file published in the GitHub repository edgard/home-ops (10 stars, last pushed 3d ago), licensed MIT. It adds 2,581 tokens to every session, about $0.0129 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
home-ops AGENTS.md
AGENTS.md instructions for gavinmcfall/home-ops, covering ai assistant configuration, 📚 documentation location, 📖 read first, ⚠️ critical invariants and capsule: gitopsreconciliation.
home-ops copilot-instructions.md
Instructions for GitHub Copilot when working with this homelab repository.
talos-argocd-proxmox CLAUDE.md
Claude Code instructions for mitchross/talos-argocd-proxmox, covering claude.md, project overview, core architecture pattern: gitops self-management, sync wave architecture and secret management flow.
talos-argocd-proxmox AGENTS.md
AGENTS.md instructions for mitchross/talos-argocd-proxmox, covering agent instructions, repo rules live in claude.md and mink knowledge capture.
mcp-k8s-observability-argocd-server AGENTS.md
AGENTS.md instructions for peopleforrester/mcp-k8s-observability-argocd-server, covering argocd mcp server, commands, tool implementation guidelines, progressive disclosure tiers and safety patterns.
mcp-k8s-observability-argocd-server CLAUDE.md
Claude Code instructions for peopleforrester/mcp-k8s-observability-argocd-server, a project described as: Safety-first ArgoCD MCP server with progressive disclosure, multi-cluster intelligence, and enterprise-grade observability.