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 skills add dungnotnull/hybrid-harness-chaos-process-prm --skill s10-gitopsgit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/skills/dungnotnull/hybrid-harness-chaos-process-prm/s10-gitops)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s10-gitops"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s10-gitops/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/skills/dungnotnull/hybrid-harness-chaos-process-prm/s10-gitops"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s10-gitops.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.00107 | $0.02424 |
| Opus 5 | $0.00053 | $0.01212 |
| Sonnet 5 | $0.00021 | $0.00485 |
| Haiku 4.5 | $0.00011 | $0.00242 |
Grade A, and why
harness-gitops 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 12d 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness GitOps
Purpose
Establish Git as the single source of truth for Kubernetes cluster state. All changes flow through Git PRs — never direct kubectl apply. Harness GitOps continuously reconciles cluster state to match the Git repository.
Input Contract
| Input | Source | Required |
|---|---|---|
| Service definitions | s05 (workflow_context.artifacts) | Yes |
| Deploy templates | s09 output | No |
| Pipeline YAML | s04 output | Yes |
| Git repository details | s01 or user | Yes |
| GitOps preference (s02 taste) | s02 taste (deployment category) | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| GitOps Application YAML | .commandcode/artifacts/app-<service>.yaml |
YAML |
| ApplicationSet YAML | .commandcode/artifacts/applicationset.yaml |
YAML |
| GitOps Agent config | .commandcode/artifacts/gitops-agent.yaml |
YAML |
| Drift alert notification rule | s21 (alerting context) | YAML |
| Pipeline GitOps sync step | s04 (pipeline updates) | YAML |
Prerequisites
- Kubernetes cluster accessible by Harness delegate
- Git repository with Kubernetes manifests or Helm charts
- Harness GitOps Agent installed in cluster
- ArgoCD CRDs installed (done automatically by Harness GitOps agent)
GitOps Architecture
Developer
│ git push / PR merge → main branch
▼
Git Repository (GitHub / GitLab / Bitbucket)
│ Harness GitOps watches for changes
▼
Harness GitOps (ArgoCD engine)
│ Detects drift OR manual sync triggered
▼
Harness GitOps Agent (runs in cluster)
│ Applies manifests via kubectl
▼
Kubernetes Cluster
│ Reconciles to match Git state
▼
Drift Alert → Harness notification → Auto-heal OR manual review
Step 1 — Install GitOps Agent
# Generate agent token in Harness UI:
# GitOps → Agents → New Agent → Kubernetes → Download YAML
# Apply to cluster
kubectl apply -f harness-gitops-agent.yaml
# Verify
kubectl get pods -n harness-gitops-agent
# Expected: gitops-agent-xxxx Running
kubectl logs -n harness-gitops-agent <AGENT_POD> | grep -i "registered"
# Expected: "Agent registered successfully"
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.
- 12d ago First seen · 361 lines · 107 tokens per session scan A dd3725cf1bd8
harness-gitops is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 107 tokens to every session and 2,424 once invoked, about $0.0005 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-30.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
release
Used to release all toolbox, integrations, agents. Use when releasing a subproject to PyPI, Docker Hub, or when the user asks to release or publish.
argocd-gitops
Implement GitOps with ArgoCD for declarative Kubernetes deployments. Configure applications, manage sync policies, implement progressive delivery, and automate deployments from Git repositories. Use when implementing GitOps workflows or continuous deployment to Kubernetes.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.