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 ClickHouse/agent-skills --skill clickstack-otel-collectorgit clone --depth 1 https://github.com/ClickHouse/agent-skillsWrote 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/clickhouse/agent-skills/clickstack-otel-collector)<a href="https://agentmods.dev/skills/clickhouse/agent-skills/clickstack-otel-collector"><img src="https://agentmods.dev/badge/skills/clickhouse/agent-skills/clickstack-otel-collector/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/clickhouse/agent-skills/clickstack-otel-collector"><img src="https://agentmods.dev/badge/skills/clickhouse/agent-skills/clickstack-otel-collector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00065 | $0.09839 |
| Opus 5 | $0.00032 | $0.04920 |
| Sonnet 5 | $0.00013 | $0.01968 |
| Haiku 4.5 | $0.00006 | $0.00984 |
Grade D, and why
clickstack-otel-collector scanned grade D with 3 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
mkdir -p "$WORKDIR" && chmod 700 "$WORKDIR" Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- The `clickhousectl` install in Step 3 uses `curl … | sh`, which many agent sandboxes flag as Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `curl …` | local health check against `localhost:13133` (and installing `clickhousectl` if missing) | new-collector path | How it starts
The opening of the file, as written. The whole thing — 855 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up an OpenTelemetry collector for Managed ClickStack
This skill wires an OpenTelemetry collector into a Managed ClickStack service running on
ClickHouse Cloud, sends rich synthetic telemetry through it, and confirms the data is actually
visible in ClickStack. It uses clickhousectl
for all cloud and SQL operations.
Scope. This skill supports two paths, chosen in Step 0:
- Deploy a new collector locally. You can do this two ways: individual
dockercommands, or adocker composefile (recommended, fewer commands and one file to start/stop). Make the user aware of both up front and let them pick in Step 0; do not assume plaindocker. Either way runs the ClickStack distribution of the collector, preconfigured for Managed ClickStack. - Configure your own existing collector by adding the ClickHouse exporter configuration. We give you the exact config to drop in; you reload your collector. Use this if you already run a collector in a gateway role.
A full Kubernetes deployment (Helm, secrets in K8s Secrets) is out of scope here; the config we generate in path 2 can be applied to a collector running anywhere.
The end state is:
- A dedicated
hyperdx_ingestSQL user on the target service, with exactly the grants the collector needs (it creates theotel.*schema on first write). - A collector forwarding logs, traces, and metrics into the
oteldatabase on the service, either the new local ClickStack collector or your existing one. - Rich synthetic telemetry across several services, severities, span statuses, and metric types, so ClickStack's Search, Service Map, and dashboards have something real to show.
- The service confirmed awake, and the user walked through the ClickStack onboarding in the Cloud console so they can actually see their data.
Secrets (the OTLP auth token and the SQL password) are generated locally, written once to a
0600 env file, and passed to Docker via --env-file. They are never pasted into the chat,
never passed with docker run -e, and never echoed back after creation.
Follow these steps in order. Each step depends on state established by the previous one.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 855 lines · 65 tokens per session scan D 28b70cb21e67
clickstack-otel-collector is a skill published in the GitHub repository ClickHouse/agent-skills (530 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 9,839 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, 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
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
azure-resource-manager-mysql-dotnet
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database…
azure-eventhub-dotnet
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming"…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".