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 skills/the-hugin/rsim/docker-deploynpx skills add the-hugin/RSIm --skill docker-deploygit clone --depth 1 https://github.com/the-hugin/RSImWrote 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/the-hugin/rsim/docker-deploy)<a href="https://agentmods.dev/skills/the-hugin/rsim/docker-deploy"><img src="https://agentmods.dev/badge/skills/the-hugin/rsim/docker-deploy.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.00031 | $0.01878 |
| Opus 5 | $0.00015 | $0.00939 |
| Sonnet 5 | $0.00006 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
docker-deploy scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
r = requests.get(f"https://{DOMAIN}/api/status", timeout=10) The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 211 lines · 31 tokens per session scan A 19a9f0e4d48e
docker-deploy is a skill published in the GitHub repository the-hugin/RSIm (2 stars, last pushed 5mo ago), with no licence file. It adds 31 tokens to every session and 1,878 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deploy-mcp
Deploy the FutureSearch MCP server to staging or production on GKE. Use when the user wants to deploy, redeploy, roll back, scale replicas, or check deployment status. Triggers on deploy, redeploy, staging, production, rollout, scale, replicas.
container-execution
Infrastructure skill for containerized target execution. Runtime detection, container lifecycle, security restrictions, interaction patterns.
vibe-ship
Generates a complete, production-ready deployment setup for any app in one pass -- Dockerfile, docker-compose.yml, .dockerignore, CI/CD (GitHub Actions), scalability config (health checks, resource limits, K8s on request), and security hardening (non-root user, secrets, dependency scanning). Auto-detects the stack…
dockerhub
Use for Docker image and container registry searches when query involves Docker images, containers, or deployment artifacts.
infra-standards
Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…
deploy-from-stale-worktree-silent-rollback
Diagnose "I deployed a new Cloud Run / Docker image but a bunch of recently merged fixes regressed in production." Use when: (1) the deploy script does gcloud builds submit ... "${SCRIPTDIR}" or docker build (build context = local filesystem, NOT a git ref), (2) the user has many git worktrees / multiple checkouts of…