Borrowing it
Nothing to install: this file belongs to boettiger-lab/data-workflows. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/boettiger-lab/data-workflows/main/.claude/skills/pod-preemption/SKILL.mdgit clone --depth 1 https://github.com/boettiger-lab/data-workflowsWrote 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/boettiger-lab/data-workflows/pod-preemption)<a href="https://agentmods.dev/skills/boettiger-lab/data-workflows/pod-preemption"><img src="https://agentmods.dev/badge/skills/boettiger-lab/data-workflows/pod-preemption/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/boettiger-lab/data-workflows/pod-preemption"><img src="https://agentmods.dev/badge/skills/boettiger-lab/data-workflows/pod-preemption.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.00180 | $0.03780 |
| Opus 5.5 | $0.00072 | $0.01512 |
| Sonnet 5.5 | $0.00036 | $0.00756 |
| Haiku 4.5 | $0.00018 | $0.00378 |
Grade A, and why
pod-preemption scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://s3-west.nrp-nautilus.io/<bucket>?list-type=2&prefix=<path>/hex/h0=<cell>/" \ How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pod Preemption
The tell: failed far exceeds the number of failed indexes
An indexed Job reports both counts. Read them together:
kubectl -n geo-workflows get job <name> \
-o jsonpath='succeeded={.status.succeeded} failed={.status.failed} failedIndexes={.status.failedIndexes}{"\n"}'
A real example from the CHELSA build (data-workflows #564):
succeeded=120 failed=47 failedIndexes=39,43
122 indices, only two ultimately failed — so roughly 45 pods died and were retried
successfully. That ~28% pod mortality is the signal. failed counts pod deaths, not indices;
when it is many times larger than len(failedIndexes), the work is fine and the pods are being
killed underneath it.
A job can even report Complete=True while this is happening. Retries hide it. Check the gap
on every long job, not just failing ones.
⛔ The gap is necessary, not sufficient — OOM-and-reroute looks identical
A wide failed vs failedIndexes gap says pods died and retried. It does not say why. A
pipeline with an expected-OOM tier — dense partitions that fail at the normal memory limit and are
rerouted to a bigger companion job — produces exactly the same shape, which is also why such jobs
carry a deliberately loose maxFailedIndexes.
The GBIF 2026-09 consolidate (data-workflows #662)
read succeeded=114 failed=47 failedIndexes=4,12,15,19-21,34 — near-identical to the #564
signature below, same failed=47. It was not preemption. Do not let that number pattern-match
you into the wrong answer; it cost a session here exactly that.
Two checks settle it before you touch the data:
- A clean earlier stage in the same window rules preemption out. Stage 1 of that job ran
succeeded=200 failed=0at default priority, same namespace, same node pool, same window as Stage 2's 47 deaths. Preemption does not selectively spare one stage. - Size correlation is the positive tell for OOM. Every failed index was among the largest partitions — the seven held 2.6B of 3.57B rows. Preemption hits indexes without regard to size; OOM hits the big ones and only the big ones.
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.
- 8d ago Changed · +1 lines 63c1ba5286d0
- 10d ago Changed · +38 lines · +31 tokens per session 11a279401108
- 1mo ago Changed · +68 lines · +44 tokens per session 2e5dea0e7a09
- 2mo ago First seen · 148 lines · 105 tokens per session scan A 07a1bf8739c1
pod-preemption is a skill published in the GitHub repository boettiger-lab/data-workflows (5 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 180 tokens to every session and 3,780 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
pod-preemption compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pod-preemptionboettiger-lab/data-workflows | Skill | 5 | 2d ago | BSD-3-Clause | A | 180 | Claude Code |
| deploy-docker-composeomnigent-ai/omnigent | Skill | 11k | yesterday | Apache-2.0 | A | 84 | Claude Code, Codex |
| bdd-container-updateNVIDIA-AI-Blueprints/video-search-and-summarization | Skill | 2.0k | yesterday | Apache-2.0 | A | 117 | Cursor |
| securing-kubernetes-on-cloudxalgorix/xalgorix | Skill | 1.3k | yesterday | Apache-2.0 | A | 80 | Claude Code, Codex |
| detecting-privilege-escalation-in-kubernetes-podsxalgorix/xalgorix | Skill | 1.3k | yesterday | Apache-2.0 | A | 40 | Claude Code, Codex |
| docker-socket-mountPurpleAILAB/Decepticon | Skill | 6.5k | 8d ago | Apache-2.0 | B | 67 | Claude Code |
| k8s-networkingrohitg00/kubectl-mcp-server | Skill | 968 | 15d ago | MIT | A | 34 | Claude Code, Codex |