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 metaspartan/cybara --skill container-operationsgit clone --depth 1 https://github.com/metaspartan/cybaraWrote 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/metaspartan/cybara/container-operations)<a href="https://agentmods.dev/skills/metaspartan/cybara/container-operations"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/container-operations.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00248 |
| Opus 5 | $0.00014 | $0.00124 |
| Sonnet 5 | $0.00006 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
container-operations 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 7d 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
Container operations
Use the available container runtime for reproducible builds, local stacks, diagnostics, and deployment validation.
Workflow
- Detect the available runtime and inspect the repository's container and Compose files before running commands.
- Validate configuration, resolved environment, mounts, ports, health checks, and dependency ordering.
- Build with explicit tags and capture build failures from the first relevant error.
- Start the smallest required service set and wait on health rather than process existence.
- Inspect service status, bounded logs, resource usage, networks, and volumes when diagnosing failures.
- Exercise the exposed application endpoint and stop temporary resources when validation is complete.
Safety
- Confirm before pruning global images, builders, volumes, or networks.
- Never print secret environment values or copy credential files into an image.
- Prefer project-scoped cleanup over global cleanup.
- Preserve persistent volumes unless the user explicitly requests deletion.
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.
- 7d ago First seen · 26 lines · 28 tokens per session scan A c98b7305ecb3
container-operations is a skill published in the GitHub repository metaspartan/cybara (28 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 248 once invoked, about $0.0001 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-30.
Other skills, from other repositories
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.
loom-kustomize
Kubernetes-native configuration management with Kustomize.
hatch3r-containerize
Containerizes an application through a repeatable workflow — multi-stage Dockerfile, non-root hardening, minimal base image, .dockerignore, healthcheck, local docker-compose, Kubernetes manifest basics, and an image-scan gate. Use when adding or hardening container artifacts.
vigilante-issue-implementation-on-kubernetes
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Kubernetes-focused repository with manifest hardening and workload security guidance.
docker-compose-launch
Launch worktree-scoped local services for issue implementation when a monorepo skill requires database dependencies.
kubernetes-best-practices
Provides production-ready Kubernetes manifest guidance including resource management, security, high availability, and configuration best practices. This skill should be used when working with Kubernetes YAML files, deployments, pods, services, or when users mention k8s, container orchestration, or cloud-native…