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 resolve-ai-oss/resolve-ai-plugins --skill satellite-configsgit clone --depth 1 https://github.com/resolve-ai-oss/resolve-ai-pluginsWrote 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/resolve-ai-oss/resolve-ai-plugins/satellite-configs)<a href="https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/satellite-configs"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/satellite-configs/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/resolve-ai-oss/resolve-ai-plugins/satellite-configs"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/satellite-configs.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.00078 | $0.00942 |
| Opus 5 | $0.00039 | $0.00471 |
| Sonnet 5 | $0.00016 | $0.00188 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
satellite-configs 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 10d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit satellite Helm values
Resolve satellites run in the customer's Kubernetes cluster. Their configuration lives in a Helm values.yaml the customer owns. This skill helps the user edit that file correctly — for adding integrations, configuring networking, or tuning resource settings.
This is a local-file-editing skill — it doesn't call Resolve MCP tools. The flow is:
- Find the
values.yaml(typicallyhelm/values/satellite/<env>/values.yamlin the customer's infra repo, or wherever they manage their Helm releases). - Make the edit.
- Apply via
helm upgrade(the user handles deploy — you don't run it). - Verify the satellite picks up the change by asking Resolve (
resolve-ai-admin:debug-integration) to inspect the satellite-backed integration.
Arguments
If $ARGUMENTS is non-empty, treat it as the task description and proceed.
If $ARGUMENTS is empty, ask the user what they want to change. Treat their next reply as the input.
Common edits
Adding a satellite-backed integration
Satellite integrations live under the integrations: block in the values.yaml. Pattern:
integrations:
<integration-key>:
type: <integration-key>
create: true
connection:
url: <url>
# ... other fields per the integration's connection schema
To learn the exact connection schema for a given integration, ask Resolve via resolve-ai:ask ("What fields does the Tempo connection schema require?"). The agent will return the schema with field descriptions.
For the supported integration keys + example connection shapes, ask Resolve via resolve-ai:ask (e.g. "List the supported integration keys with an example connection for each").
Configuring satellite networking
Satellite pods need to reach (a) Resolve cloud and (b) the customer's internal services (their Grafana, their Prometheus, etc.). Common knobs:
satellite.proxy.*— outbound HTTP proxy if the customer requires one for egresssatellite.tls.*— custom CA bundle for internal HTTPS endpoints with private certssatellite.networkPolicy.*— NetworkPolicies allowing the satellite namespace to reach customer-side services
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.
- 10d ago First seen · 79 lines · 78 tokens per session scan A 7faee197f4e8
satellite-configs is a skill published in the GitHub repository resolve-ai-oss/resolve-ai-plugins (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 78 tokens to every session and 942 once invoked, about $0.0004 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…