TotalSegmentator AGENTS.md

Instructions for using TotalSegmentator, a medical-imaging tool that identifies structures in CT or MR scans. They explain how automation and coding agents can discover supported tasks, run a scan segmentation, and read a machine-readable report.

In plain words
What is it for?
Use them in scripts and pipelines that segment medical images with TotalSegmentator. They help find available tasks, map output classes, run segmentation, and check versions, devices, and generated files.
Why use it?
They reduce reliance on hard-coded task and class names or human-readable terminal output. This makes automated runs easier to reproduce and inspect.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/wasserth/totalsegmentator/agents-md
Clone the repo
git clone --depth 1 https://github.com/wasserth/TotalSegmentator

Made for: Codex, OpenCode.

Per session 1,221 This file is loaded in full into every session.
When invoked 1,221 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01221 $0.01221
Opus 5 $0.00611 $0.00611
Sonnet 5 $0.00244 $0.00244
Haiku 4.5 $0.00122 $0.00122

Measured today against content hash 5a113e32fc31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

TotalSegmentator AGENTS.md 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 today.

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.md · 101 lines

How it starts

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

Using TotalSegmentator from automation and AI coding agents

This file is for scripts, pipelines and AI coding agents (e.g. Codex, Claude Code) that drive TotalSegmentator non-interactively. It documents how to discover the tool's capabilities, invoke it reproducibly and parse its results without scraping human-readable stdout.

For the full feature documentation see README.md.

TL;DR

# 1. Discover what the tool can do (instant, no GPU, no model download):
totalseg_info --json                       # full capability registry as JSON

# 2. Run a segmentation and capture a machine-readable run report:
TotalSegmentator -i ct.nii.gz -o seg/ --report seg/run_report.json

# 3. Read seg/run_report.json to learn versions, device, classes and output files.

Discovering capabilities

Do not hard-code task names or class names from the source. Query them instead — the data is generated from the same registry the CLI validates against, so it never drifts.

  • totalseg_info --list-tasks — table of every task (modality CT/MR, whether a license is required, number of classes).
  • totalseg_info --classes -ta <task> — the index -> class_name map a task outputs. The class names are exactly what --roi_subset expects.
  • totalseg_info --json — full registry as JSON: { "totalsegmentator_version", "tasks": { <task>: { "modality", "license_required", "classes": { "<index>": "<name>" } } } }.
  • Add --json to --list-tasks or --classes to scope the JSON to just that view.

totalseg_info imports no heavy dependencies, needs no GPU and downloads no weights, so it is safe to call at planning time to decide which task/classes to request.

The same lists are available on the main command (TotalSegmentator --list-tasks, TotalSegmentator --list-classes [task]), but those load the full runtime; prefer totalseg_info for quick discovery.

Running a segmentation

TotalSegmentator -i <input> -o <output> -ta <task> [options]
  • -i accepts a NIfTI file (.nii / .nii.gz), a folder of DICOM slices, or a zip of DICOM slices. -o is a directory of per-class masks, or a single file when --ml (multilabel), dicom_seg or dicom_rtstruct output is used.
  • -d cpu|gpu|gpu:N|mps selects the device. Without a GPU the run falls back to CPU (slow); --fast (3mm) or --roi_subset <classes> reduce runtime and memory.
  • --save_lowres writes the segmentation at the model spacing (1.5mm by default, 3mm with --fast, 6mm with --fastest) instead of resampling back to the input resolution.
  • Some tasks require a license (see license_required in the registry). Set it once with totalseg_set_license -l <key>; free non-commercial licenses: https://backend.totalsegmentator.com/license-academic/

Read the full file on GitHub · 101 lines

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.

  1. today Changed · +2 lines · +48 tokens per session 5a113e32fc31
  2. 2d ago First seen · 99 lines · 1,173 tokens per session scan A b00ddfe710f1

Subscribe to this mod's changes

TotalSegmentator AGENTS.md is an instructions file published in the GitHub repository wasserth/TotalSegmentator (2,960 stars, last pushed today), licensed Apache-2.0. It adds 1,221 tokens to every session, about $0.0061 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.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens