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.
git 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-drift)<a href="https://agentmods.dev/commands/kubestellar/kubestellar-mcp/gitops-drift"><img src="https://agentmods.dev/badge/commands/kubestellar/kubestellar-mcp/gitops-drift/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/commands/kubestellar/kubestellar-mcp/gitops-drift"><img src="https://agentmods.dev/badge/commands/kubestellar/kubestellar-mcp/gitops-drift.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.00000 | $0.00233 |
| Opus 5.5 | $0.00000 | $0.00093 |
| Sonnet 5.5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
gitops-drift 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 1mo 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 Drift Detection
Detect drift between git manifests and what's actually deployed in your clusters.
Usage
Compare your git repository against cluster state to find configuration drift.
Examples
- "Are my clusters in sync with git?"
- "Check for drift from github.com/myorg/manifests"
- "What's different between git and production?"
- "Find configuration drift in my clusters"
What it shows
- Missing resources (in git but not in cluster)
- Modified resources (differ between git and cluster)
- Specific field differences
MCP Tools Used
detect_drift- Compare git manifests against cluster state
Implementation
Use detect_drift with:
repo: Git repository URL (required)path: Path within repo (optional)branch: Branch name (default: main)clusters: Target clusters (all if not specified)
Drift Types
- missing: Resource exists in git but not in cluster
- modified: Resource exists in both but fields differ
- extra: Resource exists in cluster but not in git (not yet implemented)
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.
- 1mo ago First seen · 39 lines · 0 tokens per session scan A a0c3352705c5
gitops-drift 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 233 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
deploy
A deployment command for updating the Jarvis system and checking that its services still run. Deployment means applying code or configuration changes to a running system.
frankx-ai-deploy
Deploy FrankX.AI website changes to Vercel with quality checks.
deploy
Deploy the current project to Vercel. Pass "prod" or "production" as argument to deploy to production. Default is preview deployment.
pg-imersao-publicar
Dia 3 · PUBLICAR — GitHub + Railway. Prova, uso e manutenção (onda 2 sem reinstalar).
ship-deployment
This file contains platform-specific deployment and validation for /ship.
ship
Commit all staged and unstaged changes, push, create a PR, merge, deploy, and warm caches.