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 NVIDIA-TAO/tao-skill-bank --skill tao-prepare-anomalygennext-inputsgit clone --depth 1 https://github.com/NVIDIA-TAO/tao-skill-bankWrote 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/nvidia-tao/tao-skill-bank/tao-prepare-anomalygennext-inputs)<a href="https://agentmods.dev/skills/nvidia-tao/tao-skill-bank/tao-prepare-anomalygennext-inputs"><img src="https://agentmods.dev/badge/skills/nvidia-tao/tao-skill-bank/tao-prepare-anomalygennext-inputs/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/nvidia-tao/tao-skill-bank/tao-prepare-anomalygennext-inputs"><img src="https://agentmods.dev/badge/skills/nvidia-tao/tao-skill-bank/tao-prepare-anomalygennext-inputs.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.00059 | $0.00846 |
| Opus 5 | $0.00030 | $0.00423 |
| Sonnet 5 | $0.00012 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
tao-prepare-anomalygennext-inputs 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare AnomalyGenNext Inputs
The first action freezes eligible false-negative identities, isolates each FN mask to its bounding box, selects one deterministic same-type mask, and emits the clean and FN embedding specs. The second action consumes those embedding results, preserves every FN-to-clean pair, and runs native automatic mask placement (AMP) from the AnomalyGenNext container. The final action accepts only pairs for which both mask branches passed AMP, then freezes the exact generation inputs and their hashes.
Input contract
Start from assets/default_filtering.yaml. The gap parquet must contain:
image_id filepath gap_type bbox class split
dataset_id texture_id defect_class anomaly_type fn_mask_source
Identity is explicit: anomaly_type must equal
texture_id+defect_class. Preparation intentionally has no filename or
directory-layout inference. A caller adapting an unfamiliar dataset must
normalize these fields before this boundary.
Each selected dataset maps to an existing fine-tuned checkpoint and recipe.
The recipe must declare the exact anomaly type, and defect_spec.jsonl must
contain its placement definition. Text-routed definitions require a nonempty
roi_prompt_defect_location. The pool layout is:
POOL/TEXTURE/clean_image/*
POOL/TEXTURE/mask/DEFECT/*
Action
Run through the selected platform after the common launch review:
scripts/prepare_anomalygennext_inputs.py \
--config /path/to/filtering.yaml \
--output-dir /new/result/root
The output root must not exist. The action emits fn_queries.parquet,
selected_fn_queries.parquet, mask_selection.parquet, clean_pool.parquet,
two tao-generate-image-embeddings specs, the copied filtering config, and
input_contract.json.
Run both emitted specs through tao-generate-image-embeddings, preserving the
same encoder. Place their outputs under embeddings/ as named by the specs,
then submit the run_amp action:
scripts/run_anomalygennext_amp.py \
--config /path/to/filtering.yaml \
--prepared-root /existing/result/root
What ships with it
10 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.
- assets/default_filtering.yaml 1.0 KB
- evals/evals.json 931 B
- references/input-contract.md 1.8 KB
- references/skill_info.yaml 1.5 KB
- scripts/finalize_anomalygennext_inputs.py 9.6 KB runs code
- scripts/prepare_anomalygennext_inputs.py 11 KB runs code
- scripts/run_anomalygennext_amp.py 6.6 KB runs code
- scripts/tests/test_finalize_anomalygennext_inputs.py 4.5 KB runs code
- scripts/tests/test_prepare_anomalygennext_inputs.py 4.6 KB runs code
- scripts/tests/test_run_anomalygennext_amp.py 2.8 KB runs code
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.
- 2d ago First seen · 99 lines · 59 tokens per session scan A 320354db4ebf
tao-prepare-anomalygennext-inputs is a skill published in the GitHub repository NVIDIA-TAO/tao-skill-bank (88 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 846 once invoked, about $0.0003 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-09-10.
Other skills, from other repositories
Data Validation
Data quality checks to run before modeling — distribution summaries, leakage detection, class balance.
arboreto
Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for…
pyhealth
Build clinical/healthcare deep-learning pipelines with PyHealth — loading EHR/signal/imaging datasets (MIMIC-III/IV, eICU, OMOP, SleepEDF, ChestXray14, EHRShot), defining tasks (mortality, readmission, length-of-stay, drug recommendation, sleep staging, ICD coding, EEG events), instantiating models (Transformer…
torchdrug
Build and troubleshoot TorchDrug 0.2.1 workflows for molecular graphs, property prediction, self-supervised pretraining, molecule generation, retrosynthesis, protein representation learning, and knowledge graph reasoning. Use when code imports torchdrug or needs its datasets, models, tasks, or Engine.
deepspot-m
Generate transcriptome-wide virtual spatial transcriptomics from H&E histology with DeepSpot-M. Use when you need spatial gene expression in log1p-CPM for 224x224 tiles at about 20x, want to query protein-coding genes by symbol instead of a fixed panel, or want to run prediction across a whole slide after tiling with…
nemo-mbridge-perf-expert-parallel-overlap
Validate and use MoE expert-parallel communication overlap in Megatron-Bridge, including overlapmoeexpertparallelcomm, delaywgradcompute, and flex dispatcher backends such as DeepEP and HybridEP.