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/cwensel/arcaneum/arc-containernpx skills add cwensel/arcaneum --skill arc-containergit clone --depth 1 https://github.com/cwensel/arcaneumWrote 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/cwensel/arcaneum/arc-container)<a href="https://agentmods.dev/skills/cwensel/arcaneum/arc-container"><img src="https://agentmods.dev/badge/skills/cwensel/arcaneum/arc-container.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.1 | $0.00041 | $0.00374 |
| Opus 5 | $0.00020 | $0.00187 |
| Sonnet 5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
arc-container 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 5d 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 Management
Manages Qdrant and MeiliSearch Docker containers for local development.
# Start services
arc container start # Start both Qdrant and MeiliSearch
arc container start --service qdrant # Start only Qdrant
arc container start --service meilisearch # Start only MeiliSearch
# Stop services
arc container stop
arc container stop --service qdrant
arc container stop --service meilisearch
# Restart services
arc container restart
arc container restart --service qdrant
# Check status
arc container status
arc container status --json
# View logs
arc container logs # Tail logs from both services
arc container logs --service qdrant # Qdrant logs only
arc container logs --lines 100 # Show more lines
# Reset (delete all data)
arc container reset --confirm # Reset both services
arc container reset --service qdrant --confirm # Reset only Qdrant
Service URLs
After starting:
- Qdrant: http://localhost:6333 (REST API), http://localhost:6334 (gRPC)
- MeiliSearch: http://localhost:7700
Troubleshooting
# Check if Docker is running
docker info
# Check service health
arc container status
# View recent errors
arc container logs --lines 50
# Full reset if needed
arc container reset --confirm
arc container start
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.
- 5d ago First seen · 62 lines · 41 tokens per session scan A a4fef96dd6dd
arc-container is a skill published in the GitHub repository cwensel/arcaneum (7 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 374 once invoked, about $0.0002 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
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…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
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.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
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.