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/dwmkerr/claude-code-agent/ark-devspacenpx skills add dwmkerr/claude-code-agent --skill ark-devspacegit clone --depth 1 https://github.com/dwmkerr/claude-code-agentWhat 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.00012 | $0.00604 |
| Opus 5 | $0.00006 | $0.00302 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
Ark DevSpace 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ark DevSpace
Run Ark from a cloned repository using devspace for development/PR testing.
CRITICAL: Failure Behavior
If devspace fails, you MUST STOP and report the error. Do NOT try alternative approaches like ark-cli or npm install. DevSpace failures must be diagnosed and fixed.
When to use
- Testing Ark pull requests
- Running Ark from source code
Prerequisites
- Ark repo cloned (e.g.,
/workspace/arkor/workspace/agents-at-scale-ark) - Kind cluster running (use kind-setup skill if needed)
- Verify cluster:
kubectl cluster-info
Steps
-
Navigate to ark repo
cd /workspace/ark # or /workspace/agents-at-scale-ark -
Deploy with devspace (non-interactive)
devspace deployThis deploys all components and exits. Check the exit code - if non-zero, STOP and troubleshoot.
-
Verify deployment succeeded
kubectl get pods -n ark-system kubectl get pods -n cert-manager -
Wait for pods to be ready
kubectl wait --for=condition=Ready pods --all -n ark-system --timeout=300s -
Check services
kubectl get svc -n ark-system
Troubleshooting
Check devspace logs
ls -la .devspace/logs/
cat .devspace/logs/default.log
Common failures
-
"namespace not found" - Set namespace first
devspace use namespace ark-system -
"image pull error" - Build images locally
devspace build -
Cert-manager not ready - Wait for it
kubectl wait --for=condition=Available deployment --all -n cert-manager --timeout=120s -
Cluster connectivity - Re-export kubeconfig
kind export kubeconfig --name ark-cluster --internal
If devspace exits with error
- Check the exit code and error message
- Check
.devspace/logs/for detailed logs - Check pod status:
kubectl get pods -A - Check events:
kubectl get events -A --sort-by='.lastTimestamp' - STOP and report the specific error - do not try workarounds
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.
- 2d ago First seen · 99 lines · 12 tokens per session scan A 4c23bd457975
Ark DevSpace is a skill published in the GitHub repository dwmkerr/claude-code-agent (7 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 604 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-31.
Other skills, from other repositories
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…
cloud-k8s
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
doca-container-deployment
Use this skill when the user is hands-on deploying an in-bundle DOCA service container (Argus, DMS, Firefly, or UROM service) on a BlueField — kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness, smoke-before-bulk, and the layered…