菜单
NeMo auditor CLI reference for audit configs, targets, and jobs. Use when the task involves audit configurations, audit targets, audit jobs, vulnerability scanning, probes, or `nemo auditor` CLI commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | auditor |
| description | NeMo auditor CLI reference for audit configs, targets, and jobs. Use when the task involves audit configurations, audit targets, audit jobs, vulnerability scanning, probes, or `nemo auditor` CLI commands. |
http://localhost:8080 (default)default# List workspace configs
nemo auditor configs list
# List workspace configs
nemo auditor configs list --workspace <ws>
# Create a config with a JSON payload
# The -d body includes description plus plugins, reporting, run, and system sections.
nemo auditor configs create <name> \
-d '{"description": "<description>", "plugins": {"probe_spec": "dan.AutoDANCached"}, "reporting": {}, "run": {}, "system": {"lite": true}}'
# Get a config
nemo auditor configs get <name>
# Update a config
nemo auditor configs update <name> \
-d '{"description": "<new description>", "plugins": {"probe_spec": "dan.AutoDANCached"}, "reporting": {}, "run": {}, "system": {"lite": true}}'
# Delete a config
nemo auditor configs delete <name>
Minimal example for each required field:
{"probe_spec": "dan.AutoDANCached"} — specifies which probes to run{}{} or {"generations": 5}{"lite": true}Common probe specs: dan.AutoDANCached, dan.DanInTheWild, dan.goodside
# Create a target
nemo auditor targets create <name> \
-d '{"model": "<model-name>", "type": "<type>", "description": "<description>"}'
# Create a target with a provider (for real inference endpoints)
nemo auditor targets create <name> \
-d '{"model": "<model-name>", "type": "<type>", "options": {"provider": "<provider-name>"}}'
# List targets
nemo auditor targets list
# Get a target
nemo auditor targets get <name>
# Update a target
nemo auditor targets update <name> \
-d '{"model": "<model-name>", "type": "<type>", "description": "<new description>"}'
# Delete a target
nemo auditor targets delete <name>
Target types: nim, openai
# Run an audit locally (spec references config and target as namespace/name)
nemo auditor audit run \
--spec '{"config": "default/<config-name>", "target": "default/<target-name>"}'
# Submit an audit to a configured cluster
nemo auditor audit submit \
--spec '{"config": "default/<config-name>", "target": "default/<target-name>"}'
Jobs may take a long time or remain in pending/created status. That is expected.
nemo auditor configs list — inspect configs in the active workspacenemo auditor configs create my-config -d '{...}' — createnemo auditor configs get my-config — verifynemo auditor configs update my-config -d '{...}' — updatenemo auditor configs delete my-config — deletedefault/<config> and default/<target>nemo auditor audit run --spec '{...}', or submit with nemo auditor audit submit --spec '{...}'Use NeMo Safe Synthesizer from the NMP plugin through task-specific routing: host-local GPU runs, platform job submission, configuration, troubleshooting, artifacts, privacy settings, PII replacement, and evaluation reports. Use when the user asks about safe-synthesizer, NeMo Safe Synthesizer, synthetic tabular data, DP settings, generation failures, plugin-local runs, filesets, model filesets, or `nemo safe-synthesizer` CLI commands.
Fine-tune models on NeMo Platform with `automodel`, `unsloth`, or `rl` (all `submit`-only): HF dataset conversion, filesets, model entities, and job JSON (hyperparameters, batch, schedule, optimizer) + job polling. `automodel`/`unsloth` run SFT/LoRA as Docker GPU jobs; `rl` runs DPO (preference optimization) on a Ray cluster (Kubernetes). Use for train, fine-tune, customize, SFT, LoRA, DPO, preference optimization, learning rate, epochs, or nemo customization.
Creates a new NeMo plugin from scratch. Use when starting plugin development, setting up a plugin package, registering surfaces via entry points, or asking how plugins are discovered by the platform. Trigger keywords: create plugin, new plugin, plugin setup, entry-points, plugin structure, get started, plugin discovered, entry point.
Declares HTTP authorization on NeMo Platform plugin routes with @path_rule, AuthzScope, PermissionSet, and CallerKind. Use when adding or securing a plugin route, minting permission ids, choosing PRINCIPAL vs SERVICE_PRINCIPAL callers, fixing a hard_fail bundle build from an unruled route, or migrating off get_authz_contribution. Trigger keywords: authz, authorization, permission, path_rule, AuthzScope, PermissionSet, perm, CallerKind, SERVICE_PRINCIPAL, scope, hard_fail, on_invalid_plugin, unruled route, bundle build, get_authz_contribution.
Creates background reconcile-loop controllers using NemoController. Use when implementing state-machine reconciliation, running periodic background work, managing deployment lifecycle, building service-principal entity clients for background use, or understanding controller startup/shutdown sequence. Trigger keywords: controller, NemoController, reconcile, background loop, reconcile_one, list_objects, on_startup, state machine, deployment lifecycle, service principal, interval_seconds.
Creates in-process NemoFunction surfaces for NeMo Platform plugins. Use when adding a function, declaring spec_schema, mounting function routes with add_function_routes, understanding the two CLI verbs (run / submit), or streaming NDJSON frames. Trigger keywords - function, NemoFunction, spec_schema, add_function_routes, nemo_platform_plugin.functions, two verbs, run, submit, streaming, NDJSON, FunctionContext.