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 volcengine/volcengine-skills --skill volcengine-tls-logcollectorgit clone --depth 1 https://github.com/volcengine/volcengine-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/volcengine/volcengine-skills/volcengine-tls-logcollector)<a href="https://agentmods.dev/skills/volcengine/volcengine-skills/volcengine-tls-logcollector"><img src="https://agentmods.dev/badge/skills/volcengine/volcengine-skills/volcengine-tls-logcollector/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/volcengine/volcengine-skills/volcengine-tls-logcollector"><img src="https://agentmods.dev/badge/skills/volcengine/volcengine-skills/volcengine-tls-logcollector.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00121 | $0.01396 |
| Opus 5.5 | $0.00048 | $0.00558 |
| Sonnet 5.5 | $0.00024 | $0.00279 |
| Haiku 4.5 | $0.00012 | $0.00140 |
Grade A, and why
volcengine-tls-logcollector 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcengine TLS LogCollector
Adapted from
tls-logcollectorinvolcengine-tls/ve-tls-cli(Apache-2.0). Command examples keep the upstream nativevolclog ...form; run them asve volclog ...(requiresve >= 1.1.11) with all later arguments unchanged.
Scope
Use this skill for LogCollector collection tasks. Use volcengine-tls as the generic CLI operating model and this skill as the LogCollector-specific workflow.
First classify the request:
- TLS resource or collector-rule configuration
- Linux host installation or lifecycle management
- Kubernetes DaemonSet installation
- Kubernetes Controller/CRD installation or rule management
- heartbeat, binding, parsing, or ingestion troubleshooting
If the user only asks for a plan or commands, do not change remote resources. If the user asks to execute, show the resolved target and planned writes, validate them, then perform only the authorized changes.
Required inputs
Resolve only what the selected path needs:
- runtime selector: explicit
--profile <name>,--secrets-file <path>, or intentionally selected environment credentials regionand TLSendpoint; never derive one from the other- public or private network path
- target Project, Topic, host group, and collector rule, by ID or exact name
- input source: host file, container stdout/stderr, or container file
- for Kubernetes: cluster context, namespace, workload type/name, and container selector
- installation method and version when deployment is in scope
Do not request or echo credential values in chat. Do not put AK/SK in skill files, repositories, generated manifests, or shell history.
Contract-first workflow
- Run
volclog --profile <profile> doctor; add--onlineonly when a live connectivity check is needed. - Discover exact actions with
volclog tool list <group>. - Read every selected contract with
volclog tool describe <group.action> --view full. - Read references/config-validation.md and validate representative samples before persisting a non-trivial parser, path extraction, timestamp, index delimiter, or processor configuration.
- Read references/tls-resources.md when Project, Topic, host group, collector rule, index, or binding changes are needed.
- Run write operations with
--dry-runfirst. Dry-run validates local request shape; it does not prove that the service will accept the request or that parsing semantics are correct. - Execute the authorized write once. After an ambiguous write result, reconcile with a read action instead of retrying blindly.
- Follow the environment-specific deployment reference when installation is in scope:
- Read references/verification.md and verify process or workload health, machine heartbeat, rule binding, and Topic ingestion.
What ships with it
7 files 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.
- 25d ago First seen · 103 lines · 121 tokens per session scan A 2ada679a19b7
volcengine-tls-logcollector is a skill published in the GitHub repository volcengine/volcengine-skills (22 stars, last pushed 7d ago), licensed MIT. It adds 121 tokens to every session and 1,396 once invoked, about $0.0005 per session on Opus 5.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-24.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.