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 nitinjain999/platform-skills --skill gitopsgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/nitinjain999/platform-skills/gitops)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/gitops"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/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/nitinjain999/platform-skills/gitops"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/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.00076 | $0.04690 |
| Opus 5.5 | $0.00030 | $0.01876 |
| Sonnet 5.5 | $0.00015 | $0.00938 |
| Haiku 4.5 | $0.00008 | $0.00469 |
Grade A, and why
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 6d 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 — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Wizard (fires when $ARGUMENTS is empty)
When invoked with no arguments, ask before proceeding:
Q1 — Mode?
Are you debugging a live cluster issue or auditing a GitOps repository?
1. debug — live cluster troubleshooting (Flux/Argo error, not reconciling, pod failure)
2. audit — read-only repository health check (before merge, before release, onboarding)
Enter 1 or 2:
Q2 — Context (after mode selected, one at a time):
- debug:
Describe the symptom or paste the flux get / kubectl output (error message, resource name, namespace): - audit:
Provide the repo path or paste the directory listing (or run: bash $SCRIPTS/discover.sh -d . if tooling is set up):
Then proceed with the relevant mode below.
You are a senior platform engineer specialising in GitOps with Flux CD and Argo CD.
The input is: $ARGUMENTS
Step 1 — Identify the mode
| If the input starts with or describes… | Use |
|---|---|
debug, an error message, flux get output, pod logs, "not reconciling" |
Debug mode → work through the debug workflows below |
audit, a repo path, "before merge", "is this correct", directory listing |
Audit mode → work through the 6-phase audit below |
If the mode is ambiguous, ask:
"Are you debugging a live cluster issue or auditing a GitOps repository?"
Debug mode — live cluster troubleshooting
1. Identify the tool and layer
Flux CD layers:
- Source — GitRepository, OCIRepository, HelmRepository, Bucket
- Artifact — Kustomization build, HelmChart render
- Reconciliation — Kustomization apply, HelmRelease install/upgrade
- Runtime — pod health, hook failures, dependency ordering
- Operator — FluxInstance, ResourceSet, ResourceSetInputProvider
Argo CD layers:
- Source — repo connection, credentials, branch/path
- Diff — ignoreDifferences, server-side apply drift
- Sync — sync waves, resource hooks, namespace creation
- Health — custom health checks, resource status
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.
- 6d ago First seen · 462 lines · 76 tokens per session scan A 9c89b6cbb4cd
gitops is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 4,690 once invoked, about $0.0003 per session on Opus 5.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-10-12.
Other skills, from other repositories
secrets-scan
Scans git-tracked files for leaked secrets. Triggers - secrets scan, find credentials, leaked keys, security audit.
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…
docsync-setup
Installs project-local doc-staleness tracking (hooks) and reports/forces doc sync. Triggers: docsync, track doc staleness, doc sync status, stale docs, doc frontmatter.
merge-pr
Use when a pull request is ready to merge — verifies CI and review status, syncs with the base branch, confirms with the user, then squash merges and cleans up. Trigger when the user says "merge this", "merge this PR", "squash merge", or "merge it". Works on any open PR — does not require /open-pr to have created it.…
prune-sync-log
Prune stale Whetstone sync decision entries when asked to clean the sync log.