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/agent-hellboy/mcp-runtime/k3s-public-opsnpx skills add Agent-Hellboy/mcp-runtime --skill k3s-public-opsgit clone --depth 1 https://github.com/Agent-Hellboy/mcp-runtimeWrote 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/agent-hellboy/mcp-runtime/k3s-public-ops)<a href="https://agentmods.dev/skills/agent-hellboy/mcp-runtime/k3s-public-ops"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/k3s-public-ops.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 | $0.00089 | $0.01510 |
| Opus 5 | $0.00044 | $0.00755 |
| Sonnet 5 | $0.00018 | $0.00302 |
| Haiku 4.5 | $0.00009 | $0.00151 |
Grade A, and why
k3s-public-ops 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -k -i -H "x-api-key: $ADMIN_KEY" https://registry.mcpruntime.org/v2/ How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k3s Public Ops
Use this skill for the mcpruntime.org style public k3s deployment. Prefer the
documented user-facing commands and scripts over private shortcuts.
Source Of Truth
- Env profile:
config/deployments/mcpruntime-org.env - Example profile:
config/deployments/mcpruntime-org.env.example - Runbook:
docs/k3s-deployment-runbook.md - Readiness/debug guide:
docs/cluster-readiness.md - Scripts (canonical):
hack/deploy/mcpruntime-org/{setup,clean,restore,rollout,multitenancy-test}.sh - Script index:
hack/README.md
Non-Negotiables
- Rebuild
./bin/mcp-runtimebefore setup or rollout validation. Stale CLI binaries can stamp stale registry image refs. cluster doctorusesKUBECONFIGenv, not--kubeconfig:
KUBECONFIG=/private/tmp/mcpruntime-k3s.yaml ./bin/mcp-runtime cluster doctor
- For public bundled HTTPS, platform and tenant pull refs should use the
TLS-covered hostname, for example
registry.mcpruntime.org/.... - Do not use a registry Service ClusterIP as a bundled-HTTPS pull ref unless
the cert has the matching IP SAN. The usual symptom is:
x509: cannot validate certificate for <ClusterIP> because it doesn't contain any IP SANs. - Pod DNS and node image-pull DNS are different. Pods can resolve
registry.registry.svc.cluster.local; k3s/containerd on the node usually cannot unless/etc/rancher/k3s/registries.yamlexplicitly mirrors that exact host. - Public registry ingress is auth-protected. Platform workloads using
registry.<domain>need an image pull secret; setup should create and attachmcp-runtime-registry-pullfor platform namespaces before registry auth is re-enabled. Unauthenticated pulls may fail withno basic auth credentials.
Public k3s Setup Validation
Run the actual script path:
bash -n hack/deploy/mcpruntime-org/setup.sh
bash hack/deploy/mcpruntime-org/setup.sh
KUBECONFIG=/private/tmp/mcpruntime-k3s.yaml ./bin/mcp-runtime cluster doctor
kubectl --kubeconfig /private/tmp/mcpruntime-k3s.yaml get pods -A
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 · 151 lines · 89 tokens per session scan A 02988c297468
k3s-public-ops is a skill published in the GitHub repository Agent-Hellboy/mcp-runtime (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,510 once invoked, about $0.0004 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-31.
Other skills, from other repositories
profile-app-cpu
Find what is burning CPU in a live app container without restarting it: separate the JS thread from GC and libuv, open the V8 inspector in place with SIGUSR1, take a CPU profile over CDP, and aggregate it back to the function that owns the time. Use when containers sit at their CPU cap, healthchecks time out with…
cloud-k8s
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
competition-agent-cloud
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AI-agent, prompt-injection, MCP or toolchain, cloud, container, CI/CD, and supply-chain challenges. Use when the user asks to analyze prompt-to-tool flows, retrieval poisoning, mounted secrets, deployment drift, runtime-vs-manifest…
competition-container-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is…
competition-kernel-container-escape
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for kernel attack surface, namespace and cgroup boundaries, container isolation assumptions, syscall paths, and escape primitive verification. Use when the user asks to analyze container-to-host escape paths, kernel exploit prerequisites…
competition-supply-chain
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CI/CD, registry, dependency drift, artifact provenance, image build, release pipeline, and runtime consumer challenges. Use when the user asks to trace dependency drift, registry pulls, malicious packages, build or release tampering, CI…