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 skills/harness/harness-ai/gitops-statusnpx skills add harness/harness-ai --skill gitops-statusgit clone --depth 1 https://github.com/harness/harness-aiWrote 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/harness/harness-ai/gitops-status)<a href="https://agentmods.dev/skills/harness/harness-ai/gitops-status"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/gitops-status.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.00061 | $0.01044 |
| Opus 5 | $0.00030 | $0.00522 |
| Sonnet 5 | $0.00012 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
gitops-status 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 4d 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.
This is a copy
100% identical to gitops-status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitOps Status
Monitor GitOps application health and manage sync operations via MCP.
Instructions
Step 1: Overview Dashboard
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_dashboard"
Step 2: List Applications
Call MCP tool: harness_list
Parameters:
resource_type: "gitops_application"
org_id: "<organization>"
project_id: "<project>"
Step 3: Get Application Details
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_application"
resource_id: "<app_name>"
org_id: "<organization>"
project_id: "<project>"
Step 4: Check Resource Tree
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_app_resource_tree"
resource_id: "<app_name>"
Step 5: Get Pod Logs (Debugging)
Call MCP tool: harness_get
Parameters:
resource_type: "gitops_pod_log"
resource_id: "<pod_name>"
Step 6: Check Events
Call MCP tool: harness_list
Parameters:
resource_type: "gitops_app_event"
Step 7: Trigger Sync
Call MCP tool: harness_execute
Parameters:
resource_type: "gitops_application"
action: "sync"
resource_id: "<app_name>"
org_id: "<organization>"
project_id: "<project>"
Additional Resource Types
Call MCP tool: harness_list
Parameters:
resource_type: "gitops_agent" # ArgoCD agents
resource_type: "gitops_cluster" # Connected clusters
resource_type: "gitops_repository" # Git repositories
resource_type: "gitops_applicationset" # ApplicationSets
resource_type: "gitops_managed_resource" # K8s resources
GitOps Resource Types
| Resource Type | Operations | Description |
|---|---|---|
gitops_agent |
list, get | ArgoCD instances |
gitops_application |
list, get, sync | Applications |
gitops_applicationset |
list, get | ApplicationSets |
gitops_cluster |
list, get | K8s clusters |
gitops_repository |
list, get | Git repositories |
gitops_app_event |
list | Application events |
gitops_pod_log |
get | Pod logs |
gitops_managed_resource |
list | K8s resources |
gitops_app_resource_tree |
get | Resource tree |
gitops_dashboard |
get | Overview dashboard |
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.
- 4d ago First seen · 158 lines · 61 tokens per session scan A 920dcd4bcffb
gitops-status is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 13d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,044 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gitops-status, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…