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 storj/claude-plugins --skill satellite-infragit clone --depth 1 https://github.com/storj/claude-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/storj/claude-plugins/satellite-infra)<a href="https://agentmods.dev/skills/storj/claude-plugins/satellite-infra"><img src="https://agentmods.dev/badge/skills/storj/claude-plugins/satellite-infra/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/storj/claude-plugins/satellite-infra"><img src="https://agentmods.dev/badge/skills/storj/claude-plugins/satellite-infra.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.00069 | $0.01609 |
| Opus 5.5 | $0.00028 | $0.00644 |
| Sonnet 5.5 | $0.00014 | $0.00322 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
satellite-infra 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 11d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Satellite prod deployment (storj/infra)
The infra repo is the source of truth for the intended prod state. Default local path:
~/git/storj/infra (ask the user if it is not there). Read helm/CLAUDE.md in that repo only when
this page is not enough (e.g. chart internals, how deploys run).
It shows git state, not live state — confirm with read-only kubectl get when it matters.
Layout
- Deploys use Helmfile + Helm. No ArgoCD, no kustomize. Run by Jenkins (
Jenkinsfile.satellite.v2,jenkins/satellite-deploy.groovy). - One helmfile per region:
helm/{us1,eu1,ap1,slc,qa1,nightly}.yaml.gotmpl. - Values per region and peer:
helm/satellites/<region>/satellite-<peer>.yaml. Region base:helm/satellites/<region>/satellite.yaml. Shared:helm/placement.yaml,helm/satellite-products-common.yaml. - Charts:
helm/charts/satellite-single(most peers),satellite,satellite-console,jobq. - Some parts are bare metal via Ansible, not k8s:
us1 satellite-api on
cb_pahosts (ansible/playbooks/roles/satellite-api/vars/us1.yaml) and extra repairers (ansible/playbooks/roles/repairer-docker/vars/{us1,eu1}.yaml).
Clusters (kube contexts)
| Region | Default context | Extra |
|---|---|---|
| us1 | dp-lax-us1-rke2 |
gc-bf + repair on cb-ash-k3s; repair on rh-ewr-k3s; repair on slc/ap1 clusters in namespace satellite-us1 |
| eu1 | dp-prg-eu1-rke2 |
|
| ap1 | dp-lax-ap1-rke2 |
|
| slc | dp-lax-slc-rke2 |
qa1 shares this cluster (namespace satellite-qa) |
Namespace is satellite everywhere, except us1 repairers on other clusters (satellite-us1).
Peers
Release name = Deployment name = app label, e.g. app=satellite-repair.
Image ghcr.io/storj/satellite-modular:<tag>; command /app/satellite <sub> --config-dir=/root/.local/share/storj/satellite.
The code for <sub> is satellite/run/<sub>.go in storj/storj (modular "mud" build — not cmd/satellite or satellite/api.go).
| app | <sub> |
Notes |
|---|---|---|
| satellite-api | api | HPA (us1 5–20). us1 also bare metal. |
| satellite-console | console | HPA 3–9 |
| satellite-core | core | 1 replica, chores |
| satellite-repair | repair | us1 10, eu1 50, ap1 20, slc 4; plus extra us1 releases |
| satellite-ranged-loop | ranged-loop | 1 replica, --components=...Observer |
| satellite-auditor | auditor | us1 HPA 1–6 |
| satellite-gc-sender | gc-sender | 1 replica |
| satellite-gc-bf | gc-bf-once | CronJob (us1 0 22 * * 1,3,6) |
| satellite-admin | admin | |
| satellite-change-stream | change-stream |
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.
- 11d ago First seen · 91 lines · 69 tokens per session scan A 67f88ccb500e
satellite-infra is a skill published in the GitHub repository storj/claude-plugins (3 stars, last pushed 9d ago), licensed MIT. It adds 69 tokens to every session and 1,609 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-10.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.