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 dwmkerr/claude-code-agent --skill ark-devspacegit clone --depth 1 https://github.com/dwmkerr/claude-code-agentWrote 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/dwmkerr/claude-code-agent/ark-devspace)<a href="https://agentmods.dev/skills/dwmkerr/claude-code-agent/ark-devspace"><img src="https://agentmods.dev/badge/skills/dwmkerr/claude-code-agent/ark-devspace/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/dwmkerr/claude-code-agent/ark-devspace"><img src="https://agentmods.dev/badge/skills/dwmkerr/claude-code-agent/ark-devspace.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.00012 | $0.00604 |
| Opus 5.5 | $0.00005 | $0.00242 |
| Sonnet 5.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 1mo 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.
- 1mo 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 9mo ago), licensed MIT. It adds 12 tokens to every session and 604 once invoked, about $0.0000 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-08-31.
Other skills, from other repositories
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, profile management, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger…
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
cdf-orchestration-setup
Use when the user asks to deploy, install, reinstall, redeploy, upgrade, or connect to the CDF Orchestration Airflow controller. Owns the end-to-end deploy sequence and runs the cdf-orchestration-preflight audit first. Covers make setup, controller image builds, Helm installation, controller connection…
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…
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.
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…