deploy-otel

deploy-otel is a skill for Claude Code from stacklok/toolhive-registry-server. It costs 49 tokens per session (1,150 once invoked), scanned A, a copy of deploy-otel, Apache-2.0.

A deployment workflow that installs Prometheus, Grafana, and the OpenTelemetry Collector in a Kind Kubernetes cluster. These tools collect, store, and display application monitoring data.

In plain words
What is it for?
Use it to set up monitoring tests with Kind, Helm, and kubectl, including metrics collection and dashboards for OpenTelemetry data.
Why use it?
It creates a local test environment for checking telemetry from a registry server without requiring a full production cluster.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to set up monitoring tests with Kind, Helm, and kubectl, including metrics collection and dashboards for OpenTelemetry data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stacklok/toolhive-registry-server/deploy-otel
Install

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.

Any agent
npx skills add stacklok/toolhive-registry-server --skill deploy-otel
Clone the repo
git clone --depth 1 https://github.com/stacklok/toolhive-registry-server

Made for: Claude Code.

Wrote 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.

agentmods badge for deploy-otel

README.md
[![agentmods](https://agentmods.dev/badge/skills/stacklok/toolhive-registry-server/deploy-otel/github.svg)](https://agentmods.dev/skills/stacklok/toolhive-registry-server/deploy-otel)
Your own site
<a href="https://agentmods.dev/skills/stacklok/toolhive-registry-server/deploy-otel"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive-registry-server/deploy-otel/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.

agentmods 80×15 button for deploy-otel

Your own site · 80×15
<a href="https://agentmods.dev/skills/stacklok/toolhive-registry-server/deploy-otel"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive-registry-server/deploy-otel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,150 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01150
Opus 5.5 $0.00020 $0.00460
Sonnet 5.5 $0.00010 $0.00230
Haiku 4.5 $0.00005 $0.00115

Measured 1mo ago against content hash 6dd994c47c14, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-otel 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.

Origin

This is a copy

91% identical to deploy-otel — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/deploy-otel/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy OTEL Observability Stack

Deploy a complete OpenTelemetry observability stack to a Kind cluster for testing the registry server's telemetry capabilities.

Steps

1. Verify Prerequisites

Check that required tools are installed:

echo "Checking prerequisites..."
command -v kind >/dev/null 2>&1 || { echo "ERROR: kind is not installed"; exit 1; }
command -v helm >/dev/null 2>&1 || { echo "ERROR: helm is not installed"; exit 1; }
command -v kubectl >/dev/null 2>&1 || { echo "ERROR: kubectl is not installed"; exit 1; }
echo "All prerequisites met."

2. Create Kind Cluster

Create the Kind cluster if it doesn't exist:

CLUSTER_NAME="thv-registry"

if kind get clusters 2>/dev/null | grep -q "^${CLUSTER_NAME}$"; then
  echo "Kind cluster '${CLUSTER_NAME}' already exists"
else
  echo "Creating Kind cluster '${CLUSTER_NAME}'..."
  kind create cluster --name ${CLUSTER_NAME}
fi

# Export kubeconfig
kind get kubeconfig --name ${CLUSTER_NAME} > kconfig.yaml
echo "Kubeconfig written to kconfig.yaml"

3. Add Helm Repositories

echo "Adding Helm repositories..."
helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add grafana https://grafana.github.io/helm-charts
helm repo update
echo "Helm repositories updated."

4. Install Prometheus/Grafana Stack

echo "Installing kube-prometheus-stack..."
helm upgrade -i kube-prometheus-stack prometheus-community/kube-prometheus-stack \
  -f examples/otel/prometheus-stack-values.yaml \
  -n monitoring --create-namespace \
  --kubeconfig kconfig.yaml \
  --wait --timeout 5m

echo "Prometheus/Grafana stack installed."

5. Install Tempo for Distributed Tracing

echo "Installing Grafana Tempo..."
helm upgrade -i tempo grafana/tempo \
  -f examples/otel/tempo-values.yaml \
  -n monitoring \
  --kubeconfig kconfig.yaml \
  --wait --timeout 3m

echo "Grafana Tempo installed."

Read the full file on GitHub · 159 lines

Changes

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.

  1. 1mo ago First seen · 159 lines · 49 tokens per session scan A 6dd994c47c14

Subscribe to this mod's changes

deploy-otel is a skill published in the GitHub repository stacklok/toolhive-registry-server (29 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,150 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to deploy-otel, differing in 15 lines, and is treated as a copy.

Related

Other skills, from other repositories

owasp-ai-testing

AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.

mastepanoski/claude-skills · 43 tokens

postcheck-verifier

Proves actions worked in reality — not just exit code 0, not just logs — by validating actual observable outcomes in the system.

ariffazil/arifOS · 31 tokens

ai-safe2-development-method

Plan and execute material repository changes with the AI SAFE2 development method. Use when a coding task needs a delivery-shape decision, risk-adjusted design depth, isolated implementation, test-first or explicit substitute evidence, systematic debugging, review cadence, before/after comparison, or a completion…

CyberStrategyInstitute/ai-safe2-framework · 92 tokens

golang-testing

Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.

affaan-m/ECC · 37 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 151 tokens

golang-testing

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…

samber/cc-skills-golang · 115 tokens