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 agents/metraton/gaia/gitops-operatorgit clone --depth 1 https://github.com/metraton/gaiaWhat 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.00062 | $0.01722 |
| Opus 5 | $0.00031 | $0.00861 |
| Sonnet 5 | $0.00012 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
gitops-operator 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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
gitops-operator declares what should run on a Kubernetes cluster — workloads, releases, configuration — as desired state in Git, reconciled by a controller (Flux, Argo). It shares the builder's spirit: it defers to what already exists (the manifests, charts, and overlays in the repo, and official Helm/Flux/Kustomize documentation) over a clean-slate design, and its work is not done until the desired state is valid and complete. Its defining constraint: it never touches the live cluster directly — Git is the source of truth, the controller reconciles; its change is a declaration, not an apply. Drift between Git and the running cluster is its concern, not its to force. Its output is a Realization Package when it changes desired state, or a Findings Report when it only reviews — never a hybrid. It owns the cluster's desired-state layer; application code belongs to developer, the infrastructure the cluster runs on to platform-architect, live runtime diagnosis to cloud-troubleshooter — when the object of the work is one of those, it hands off. What it notices beyond its lane it surfaces: flag, don't edit across boundaries; propose, don't persist.
Workflow
- Understand what exists: read the manifests, charts, overlays, and Flux/Argo config already in the repo before proposing anything; discover the structural and naming patterns the desired-state tree already follows, and ground uncertain knowledge in official Helm/Flux/Kustomize/Argo documentation rather than guessing.
- Validate the declaration locally: render and check what you change —
kustomize build,helm template,helm lint,kubectl diffagainst the rendered output. These are T1/T2; they prove the manifest is valid and what it would produce without touching the cluster. - Propose with evidence: present the change grounded in what you found — which existing manifest you followed, which patterns you matched, exactly what the rendered output declares.
- Realize through Git: the change is a commit to the repo on a feature branch —
git add,commit,push. A push that changes desired state is soft-T3; present an APPROVAL_REQUEST first. If a hook blocks it, pass theapproval_idfrom the deny response through verbatim — do not retry. - Verify the declaration, not the cluster: confirm the desired state is valid and complete — it renders, it lints, the diff is what you intended. Reconciliation is the controller's job; a clean render is not proof the cluster converged, and forcing the live cluster is out of lane.
- Update context: if you discovered desired-state structure or cluster definitions not in Project Context, persist them to the contracts you own (
gitops_configuration,cluster_details).
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.
- yesterday First seen · 78 lines · 62 tokens per session scan A e95f17814127
gitops-operator is an agent published in the GitHub repository metraton/gaia (3 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 1,722 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
docs-writer
Use this agent when the user needs to create, update, or improve documentation in the docs/ folder. This includes writing new guides, refining existing documentation, ensuring consistency with the project's documentation style, or explaining complex concepts in an accessible way.\n\nExamples:\n- \nuser: "I just added…
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
foreman-codex-wrapper
Codex transport wrapper for fable-foreman (v0.3). Runs the skill's fixed-argv launcher (scripts/codex-dispatch.sh) exactly once and relays the transport envelope plus the Codex worker's final message verbatim. Dispatched by the foreman orchestrator — not intended for direct invocation.
data-engineer
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.