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-configgit 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-config)<a href="https://agentmods.dev/skills/scitix/siclaw/volcano-scheduler-config"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-scheduler-config/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-config"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-scheduler-config.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.00024 | $0.02364 |
| Opus 5 | $0.00012 | $0.01182 |
| Sonnet 5 | $0.00005 | $0.00473 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
volcano-scheduler-config 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcano Scheduler Configuration
View Volcano scheduler configuration to understand scheduling policies, enabled plugins, and actions. This skill helps diagnose configuration-related scheduling behaviors.
Scope: This skill is for diagnosis only. It retrieves configuration for analysis but does not modify any cluster state.
Usage
bash skills/core/volcano-scheduler-config/scripts/get-scheduler-config.sh [options]
Parameters
| Parameter | Required | Description |
|---|---|---|
--section SECTION |
no | Show specific section: actions, plugins, tiers, all (default: all) |
--format FORMAT |
no | Output format: yaml, json, summary (default: summary) |
--raw |
no | Show raw ConfigMap data without parsing |
Examples
Get summary of scheduler configuration:
bash skills/core/volcano-scheduler-config/scripts/get-scheduler-config.sh
View actions configuration only:
bash skills/core/volcano-scheduler-config/scripts/get-scheduler-config.sh --section actions
View plugins configuration:
bash skills/core/volcano-scheduler-config/scripts/get-scheduler-config.sh --section plugins
Show full YAML configuration:
bash skills/core/volcano-scheduler-config/scripts/get-scheduler-config.sh --format yaml
Get raw ConfigMap:
bash skills/core/volcano-scheduler-config/scripts/get-scheduler-config.sh --raw
Understanding Scheduler Configuration
Configuration Location
The Volcano scheduler configuration is stored in:
- Namespace:
volcano-system - ConfigMap:
volcano-scheduler-configmap - Key:
volcano-scheduler.conf
Configuration Structure
actions: "enqueue, allocate, backfill" # Pipeline order
tiers:
- plugins:
- name: priority
- name: gang
- name: conformance
- plugins:
- name: overcommit
- name: drf
- name: predicates
- name: proportion
- name: nodeorder
- name: binpack
Actions
Actions define the two-phase scheduling pipeline:
- Enqueue phase — PodGroup is admitted to the queue based on queue capacity (does the queue have enough deserved resources?)
- Allocate phase — Individual pods are placed on nodes based on node resources, affinity, taints, etc.
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 · 372 lines · 24 tokens per session scan A 9389f3dbd522
volcano-scheduler-config is a skill published in the GitHub repository scitix/siclaw (233 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 2,364 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-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.
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.
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…
k8s-service-connectivity
A troubleshooting guide for Kubernetes service connectivity, where services provide stable network access to groups of running containers. It focuses on missing endpoints, selector mismatches, network policies, and kube-proxy problems.
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.