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/decocms/studio/self-host-studionpx skills add decocms/studio --skill self-host-studiogit clone --depth 1 https://github.com/decocms/studioWhat 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.00117 | $0.06198 |
| Opus 5 | $0.00059 | $0.03099 |
| Sonnet 5 | $0.00023 | $0.01240 |
| Haiku 4.5 | $0.00012 | $0.00620 |
Grade A, and why
self-host-studio 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
mkdir -p <name>/templates && curl -fsSL \ How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-host deco Studio
Guide a user from nothing to a running, reachable Studio on their own infra. Be interactive: detect what they have, pick ONE tier, configure the chart(s) correctly, run it, then verify it actually works (pods Running + UI reachable
- signup) — don't just report "installed".
Studio hard-needs PostgreSQL and an S3-compatible object store; NATS is bundled; the sandbox (code-exec + previews) is an optional layer.
What you produce is a directory, not a running pod. Every install — laptop
or EKS — ends with an install directory the user owns and keeps: an umbrella
chart with pinned OCI dependencies plus the values you filled in. Installing is
then helm upgrade --install on that directory, and it behaves the same on
Rancher Desktop and on a managed cluster — see "The artifact" below. Do not
clone this repo and do not install from a checkout; the charts are public OCI
artifacts and need no credentials.
0. Detect the environment
Detect what the user has:
uname -m # arm64 (Apple Silicon) or x86_64
docker version --format '{{.Server.Version}}' 2>/dev/null || echo "no docker"
kubectl config current-context 2>/dev/null || echo "no kube context"
kubectl get nodes -o custom-columns='ARCH:.status.nodeInfo.architecture' --no-headers 2>/dev/null
kubectl get storageclass 2>/dev/null # note the (default) one
helm version --short 2>/dev/null || echo "no helm"
No managed Kubernetes? Any local cluster works (all core images are multi-arch, Apple Silicon included): Rancher Desktop, Docker Desktop, k3d, kind, minikube, Colima/OrbStack.
Interview — ask, then fill a values file
Drive the install by ASKING, one question at a time; don't assume. Confirm the
detected environment, then walk these. Record answers into a values file you'll
helm template-validate and show the user before installing.
- Goal / tier — "Trying it out, a POC on a real cluster, or production?" → try-out → Compose (no artifact), or the artifact with bundled dev deps. → POC on a real cluster → the artifact, deps you choose below, dev-grade secrets OK. → production → the artifact + external secrets + HPA.
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 · 405 lines · 117 tokens per session scan A b70946cf03c2
self-host-studio is a skill published in the GitHub repository decocms/studio (402 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 6,198 once invoked, about $0.0006 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-30.
Other skills, from other repositories
mcp-assistant
Use when a task needs connected MCP servers, external services, dynamic MCP tool discovery, schema inspection, sandboxed MCP execution, or routing across many possible MCP tools.
pr-finish-pass
Final-polish pass on the current PR or feature branch before it lands. Rebases on origin/main, force-pushes, drives CI to green, then reviews the diff for correctness/perf/security/reliability bugs, flaky test patterns banned by make lint-test-patterns, sloppy comments a senior engineer would not write, cross-crate…
mcp-cli
Use when running, automating, integrating, or troubleshooting the MCP CLI (mcpa | mcp-ts), including local or remote discovery, authentication, schema inspection, tool calls, and gateway lifecycle errors.
harn-release
Use for Harn release prep, version bumps, publishing, tags, and release notes.
harn-apps
Keep app behavior in Harn while shared hosts draw the view and provide files, network, and browser features.
harn-mcp
Use for MCP client connections, server definitions, inbound roots/sampling/elicitation, and deterministic MCP fixtures.