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 commands/kubestellar/kubestellar-mcp/gitops-syncgit clone --depth 1 https://github.com/kubestellar/kubestellar-mcpWrote 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/commands/kubestellar/kubestellar-mcp/gitops-sync)<a href="https://agentmods.dev/commands/kubestellar/kubestellar-mcp/gitops-sync"><img src="https://agentmods.dev/badge/commands/kubestellar/kubestellar-mcp/gitops-sync.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.00000 | $0.00269 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
gitops-sync 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.
What it actually says
GitOps Sync
Sync manifests from a git repository to your clusters.
Usage
Provide a git repository URL and optional path, and kubestellar-deploy will apply all manifests to your clusters.
Examples
- "Sync my manifests from github.com/myorg/k8s-manifests"
- "Apply the production manifests from git to all clusters"
- "Sync from git repo github.com/org/configs path environments/prod"
- "Preview what would change if I sync from git"
What it does
- Clones the git repository (shallow clone)
- Reads all YAML/JSON manifests from the specified path
- Applies each manifest to target clusters
- Reports created/updated/unchanged counts per cluster
MCP Tools Used
sync_from_git- Apply manifests from git to clusterspreview_changes- Dry-run to see what would changereconcile- Force sync to bring clusters in line with git
Implementation
Use sync_from_git with:
repo: Git repository URL (required)path: Path within repo (optional)branch: Branch name (default: main)clusters: Target clusters (all if not specified)dry_run: Set to true to preview without applying
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 · 37 lines · 0 tokens per session scan A 51298f084b38
gitops-sync is a command published in the GitHub repository kubestellar/kubestellar-mcp (2 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 269 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.