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 scitix/siclaw --skill volcano-scheduler-logsgit clone --depth 1 https://github.com/scitix/siclawWrote 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/scitix/siclaw/volcano-scheduler-logs)<a href="https://agentmods.dev/skills/scitix/siclaw/volcano-scheduler-logs"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-scheduler-logs/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/scitix/siclaw/volcano-scheduler-logs"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-scheduler-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01675 |
| Opus 5 | $0.00015 | $0.00838 |
| Sonnet 5 | $0.00006 | $0.00335 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
volcano-scheduler-logs 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 10d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcano Scheduler Logs
Retrieve and analyze Volcano scheduler logs to understand scheduling decisions, failures, and performance issues.
Scope: This skill is for diagnosis only. It retrieves logs for analysis but does not modify any cluster state.
Usage
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh [options]
Parameters
| Parameter | Required | Description |
|---|---|---|
--keyword KEYWORD |
no | Filter logs by keyword (case-insensitive) |
--pod POD |
no | Filter logs related to specific pod name |
--since TIME |
no | Show logs newer than relative time (e.g., 10m, 1h) |
--lines N |
no | Number of lines to show (default: 100) |
--follow |
no | Stream logs in real-time (Ctrl+C to stop) |
--previous |
no | Show logs from previous container instance (after restart) |
Examples
Get recent scheduler logs:
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh
Search for error messages:
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh --keyword error
Get logs for a specific pod:
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh --pod my-job-0
Get last 500 lines from the past hour:
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh --since 1h --lines 500
Stream logs for gang scheduling issues:
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh --keyword gang --follow
Check logs from previous scheduler instance (after crash/restart):
bash skills/core/volcano-scheduler-logs/scripts/get-scheduler-logs.sh --previous --lines 200
Common Keywords for Filtering
| Keyword | Use Case |
|---|---|
error |
Find error messages and failures |
FailedScheduling |
Scheduling failures |
allocate |
Resource allocation attempts |
gang |
Gang scheduling decisions |
minMember |
MinMember constraint issues |
preempt |
Preemption events |
reclaim |
Resource reclamation |
enqueue |
Queue admission decisions |
bind |
Pod binding attempts |
queue |
Queue-related decisions |
proportion |
Proportion plugin decisions |
priority |
Priority-related decisions |
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.
- 10d ago First seen · 242 lines · 29 tokens per session scan A 791e5939a9eb
volcano-scheduler-logs is a skill published in the GitHub repository scitix/siclaw (233 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 1,675 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
k8s-deployment-rollout
A troubleshooting workflow for failed Kubernetes Deployment releases and rolling updates that become stuck. Kubernetes is a system for running and managing containers.
k8s-pod-crashloop
A troubleshooting guide for Kubernetes pods that repeatedly restart or run out of memory. Kubernetes is a system for running and managing containers, and a pod is its basic unit for running an application.
k8s-dns-failure
A guide for diagnosing and fixing DNS problems in Kubernetes, a system for running containerised applications. It focuses on CoreDNS, the component that helps services find one another and reach external services.
k8s-control-plane
A troubleshooting guide for Kubernetes control-plane failures. Kubernetes is software that manages containerised applications, while the control plane coordinates the cluster through components such as the API server, etcd, and scheduler.
incident-triage
Use when asked to triage, investigate, or diagnose a Kubernetes incident, outage, or unhealthy workload. Gives the step-by-step order of investigation and the format for the findings.
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.