What is node-scheduling?

A set of guidance for Kubernetes node scheduling: deciding where workloads run and how much CPU and memory they reserve or may use. It explains requests, limits, quality-of-service classes, throttling, out-of-memory kills, and evictions.

Use it before changing container resources, placement rules, tolerations, or topology spreading, and when investigating throttling, OOMKills, or evictions.

It prevents settings that reserve more capacity than intended, throttle containers unexpectedly, or change a workload's protection from memory pressure. It also highlights cases where chart defaults hide the real configuration.

How Aviator-Coding/home-ops configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to Aviator-Coding/home-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Aviator-Coding/home-ops/main/.agents/skills/node-scheduling/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Aviator-Coding/home-ops

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aviator-coding/home-ops/node-scheduling/github.svg)](https://agentmods.dev/skills/aviator-coding/home-ops/node-scheduling)

Your own site

<a href="https://agentmods.dev/skills/aviator-coding/home-ops/node-scheduling"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/node-scheduling/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aviator-coding/home-ops/node-scheduling"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/node-scheduling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,124 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00089	$0.01124
Opus 5.5	$0.00036	$0.00450
Sonnet 5.5	$0.00018	$0.00225
Haiku 4.5	$0.00009	$0.00112

Measured 23d ago against content hash df68ba230425, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

node-scheduling 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 23d 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.

.agents/skills/node-scheduling/SKILL.md · 41 lines

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Node scheduling: requests, limits, QoS and talos-3 placement

Tripwires

A missing requests.memory reserves the whole limits.memory. Kubernetes defaults the request to the limit before anything can read the Pod, so the live object looks identical to a deliberate Guaranteed one. Audit the Git manifest. Gate: scripts/ci/memory-request-declared-test.py. sizing-method.md
A CPU limit is a CFS quota per 100ms period, not a share of the node. Node idle does not mean the container is unthrottled. Throttling does not crash, restart, fail a probe, or OOM. Mean usage under a limit is the quota talking. Do not size a request from a coarse max_over_time(rate(...[5m])). Gate: scripts/ci/cpu-throttle-contract-test.py.
Cutting a request or raising only the limit on a requests == limits container demotes it from Guaranteed to Burstable. Talos OOMController skips Guaranteed cgroups. k8tz, cilium-agent (a kill drops the node network plane), the Rook mons and the Rook log collector hold equality on purpose (skill rook-ceph, skill system-namespaces).
limits: {} does not unset a chart default. Helm merges the empty map as a no-op. Read the chart's own values.yaml before trusting it. The Rook operator is the worked case (skill rook-ceph).
talos-3's taint is home-operations.com/dedicated: PreferNoSchedule. It is a scheduler score penalty (TaintToleration weight 3), not a filter. A hard NoSchedule strands a drain of talos-1 or talos-2 once the general fleet has rolled off. A toleration matches only when its effect equals the taint's. talos-3-ledger.md
nodeTaintsPolicy: Honor does not see PreferNoSchedule. It filters NoSchedule and NoExecute only. Leave the Honor entries; do not read them as keeping pods off talos-3.
Descheduler will not evict PreferNoSchedule violators. RemovePodsViolatingNodeTaints is on and includePreferNoSchedule is unset. Pods leave talos-3 on their own next rollout. LowNodeUtilization thresholds are 20, so it does not rebalance this node.
Do not place a new workload on talos-3, raise a request there, or drop a toleration without remeasuring. Old committed-percent figures contradict each other. Remeasure. vLLM and embedding memory belong to skill b70-llm-serving. OSD request and osd_memory_target belong to skill rook-ceph.

Read the full file on GitHub · 41 lines

Files

What ships with it

2 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.

Changes

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.

23d ago Changed df68ba230425
25d ago First seen · 41 lines · 89 tokens per session scan A 0dc8347183b0

Subscribe to this mod's changes

node-scheduling is a skill published in the GitHub repository Aviator-Coding/home-ops (3 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 1,124 once invoked, about $0.0004 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-29.

DevOps and cloud

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

home-ops: Skill for Claude Code