Apache SkyWalking BanyanDB is a database for collecting, analyzing, and storing metrics, traces, and logs produced by observability and application-performance systems. It is intended for platforms such as Apache SkyWalking that need to work with monitoring data.
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/apache/skywalking-banyandb/vendor-updatenpx skills add apache/skywalking-banyandb --skill vendor-updategit clone --depth 1 https://github.com/apache/skywalking-banyandbWrote 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/apache/skywalking-banyandb/vendor-update)<a href="https://agentmods.dev/skills/apache/skywalking-banyandb/vendor-update"><img src="https://agentmods.dev/badge/skills/apache/skywalking-banyandb/vendor-update.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.00095 | $0.00889 |
| Opus 5 | $0.00048 | $0.00445 |
| Sonnet 5 | $0.00019 | $0.00178 |
| Haiku 4.5 | $0.00010 | $0.00089 |
Grade A, and why
vendor-update 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade vendor dependencies
Run the vendor-update Make target across all projects:
make vendor-update
This runs go get -u ./... and go mod tidy -compat=1.25 in each project directory (ui, banyand, bydbctl, mcp, fodc/agent, fodc/proxy, pkg, test).
Update license dependencies
After the vendor upgrade completes, run make license-dep to update any license-related files that may have changed due to new or updated dependencies:
make license-dep
This ensures license headers and dependency license files stay in sync with the upgraded vendors.
Check for tool version drift
After upgrading, compare go.mod dependency versions against scripts/build/version.mk to find any tools whose library version was bumped and may need their tool version updated.
Version mapping
Read scripts/build/version.mk and go.mod in parallel. For each tool version variable, check if the corresponding library in go.mod was upgraded:
| version.mk variable | Binary | go.mod package |
|---|---|---|
BUF_VERSION |
bin/buf |
github.com/bufbuild/buf (if present) |
PROTOC_GEN_GO_VERSION |
bin/protoc-gen-go |
google.golang.org/protobuf |
PROTOC_GEN_GO_GRPC_VERSION |
bin/protoc-gen-go-grpc |
google.golang.org/grpc |
PROTOC_GEN_DOC_VERSION |
bin/protoc-gen-doc |
github.com/pseudomuto/protoc-gen-doc (if present) |
GRPC_GATEWAY_VERSION |
bin/protoc-gen-grpc-gateway |
github.com/grpc-ecosystem/grpc-gateway/v2 |
PROTOC_GEN_VALIDATE_VERSION |
bin/protoc-gen-validate |
github.com/envoyproxy/protoc-gen-validate |
GOLANGCI_LINT_VERSION |
bin/golangci-lint |
(no go.mod entry — only in version.mk) |
REVIVE_VERSION |
bin/revive |
(no go.mod entry — only in version.mk) |
LICENSE_EYE_VERSION |
bin/license-eye |
(no go.mod entry — only in version.mk) |
MOCKGEN_VERSION |
bin/mockgen |
go.uber.org/mock |
GINKGO_VERSION |
bin/ginkgo |
github.com/onsi/ginkgo/v2 |
GOVULNCHECK_VERSION |
bin/govulncheck |
golang.org/x/vuln |
BPF2GO_VERSION |
(used in bpf2go.mk) | github.com/cilium/ebpf |
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.
- yesterday First seen · 72 lines · 95 tokens per session scan A b69bebea0784
vendor-update is a skill published in the GitHub repository apache/skywalking-banyandb (350 stars, last pushed yesterday), licensed Apache-2.0. It adds 95 tokens to every session and 889 once invoked, about $0.0005 per session on Opus 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-09-03.
Other skills, from other repositories
golang-observability-opentelemetry
Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog.
build-audit-logs
Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews). For application code, not for extending the evlog package.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
otel-go
OpenTelemetry in Go — SDK setup, API surface, breaking changes, contrib instrumentation libraries (otelhttp, otelgrpc, otelmongo), compile-time zero-code instrumentation (otelc), and performance tuning. Use when adding, reviewing, or configuring OpenTelemetry in a Go service. Triggers on "setup otel in go", "go…
golang-grpc
Production gRPC in Go: protobuf layout, codegen, interceptors, deadlines, error codes, streaming, health checks, TLS, and testing with bufconn.
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.