Generated banner for Jetson Print Device Info
Generated logo for Jetson Print Device Info

Jetson Print Device Info

NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • Medium risk

From the author

Use when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target. This is an example skill.
— the description by Jetson Team

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a standardized method for gathering essential system information from a running NVIDIA Jetson device. It performs a read-only inspection of the device's software stack, kernel version, OS release, and current power mode. Designed as a diagnostic utility, it is intended to establish a baseline state before executing performance, regression, or compatibility tests, ensuring that the environment matches expected configurations.

What it does

  • Identifies the specific Jetson hardware model via device-tree inspection.
  • Retrieves the current L4T release version and revision.
  • Queries the active power mode and associated mode index.
  • Reports the current kernel version and system uptime.
  • Detects the underlying OS version using standard system files.
  • Validates that the host is a Jetson device before proceeding.

When to use it

  • Before running performance benchmarks to document the system state.
  • When verifying that a newly flashed device matches the target software version.
  • During troubleshooting to confirm the current power and OS configuration.
  • As a pre-test check to ensure the environment is correctly configured.

Advantages

  • Provides a consistent, human-readable report format.
  • Gracefully handles missing components without crashing.
  • Non-intrusive read-only operation ensures system stability.
  • Includes built-in validation to prevent execution on non-Jetson hardware.

Usage examples

“Print the current system information for this Jetson device.”
The agent outputs a structured report containing the model name, L4T release, power mode, kernel version, uptime, and OS version.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/jetson-print-device-info/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip jetson-print-device-info.zip -d .agents/skills

Documentation by Jetson Team

jetson-print-device-info

Prints a concise summary of the Jetson device this skill runs on.

This skill is intended as a reference example for the jetson-device-skills repo and the NVIDIA-wide skills CI. It runs on the Jetson target (not the host PC) and performs read-only inspection — useful as a baseline capture before running performance tests.

Purpose

Capture a baseline snapshot of a Jetson target's software stack and power mode before running performance, regression, or compatibility tests.

When to use

  • Starting a performance run and you want a captured baseline of the device's software stack and power mode.

  • Verifying that a freshly flashed Jetson matches an expected L4T / JetPack version.

Prerequisites

  • Running on a Jetson target (not the host PC).

  • Standard CLIs available: tr, cat, uname, uptime, lsb_release (or /etc/os-release).

  • nvpmodel available for power mode (optional — skill falls back gracefully).

Inputs

None. The skill reads only from the local Jetson filesystem and standard CLIs.

Instructions

Run each step in order and print the captured values into the report shown under Output format.

  1. Capture the module model and validate it is a Jetson target — exit early otherwise:

    # Device-tree strings are null-terminated, so strip NULs before printing.
    model=$(tr -d '\0' < /proc/device-tree/model 2>/dev/null)
    case "$model" in
      *Jetson*) ;;
      *) echo "Not running on a Jetson target (model: '${model:-unknown}')"; exit 1 ;;
    esac
    echo "$model"
  2. Extract the L4T release header line — skip the rest of the file (long list of library SHAs):

    head -1 /etc/nv_tegra_release 2>/dev/null || echo "L4T release info not found"
    # Equivalent: grep -m1 '^# R' /etc/nv_tegra_release
  3. Run nvpmodel -q and join its two output lines (NV Power Mode: <name> and the mode number) onto one line. paste -sd only uses the first char of its delimiter, so use awk to insert the literal / separator:

    nvpmodel -q 2>/dev/null | awk 'NR==1{a=$0; next} {print a" / "$0}' \
      || echo "nvpmodel not available"
  4. Print the kernel version and uptime:

    uname -r
    uptime -p
  5. Print the OS version (prefer lsb_release, fall back to /etc/os-release):

    lsb_release -ds 2>/dev/null || (. /etc/os-release && echo "$PRETTY_NAME") || echo "OS version not found"

Output format

Print a short report with these sections, one line each where possible:

Model:           <device-tree model string>
L4T release:     <release header line>
Power mode:      <nvpmodel name> / <mode number>
Kernel:          <uname -r>
Uptime:          <uptime -p>
OS version:      <lsb_release / /etc/os-release output>

Examples

Example output on an Orin AGX dev kit (L4T R36 / Ubuntu 22.04):

Model:           NVIDIA Jetson AGX Orin Developer Kit
L4T release:     # R36 (release), REVISION: 3.0
Power mode:      NV Power Mode: MAXN / 0
Kernel:          5.15.136-tegra
Uptime:          up 2 hours, 14 minutes
OS version:      Ubuntu 22.04.4 LTS

Example output on an AGX Thor (L4T R39 / Ubuntu 24.04):

Model:           NVIDIA Jetson AGX Thor Developer Kit
L4T release:     # R39 (release), REVISION: 0.0
Power mode:      NV Power Mode: 120W / 1
Kernel:          6.8.0-tegra
Uptime:          up 12 minutes
OS version:      Ubuntu 24.04 LTS

Error handling

Each command falls back to a clearly labeled "... not found" / "... not available" string if the underlying file or binary is missing — the skill never errors out mid-report. If /proc/device-tree/model is missing or does not contain a Jetson string, exit early with a clear "not running on a Jetson target" message.

Limitations

  • Read-only inspection only — does not detect GPU/CPU clocks, thermal state, or per-rail power.

  • nvpmodel output format varies between L4T versions; the skill prints it verbatim rather than parsing.

Troubleshooting

  • Error: /proc/device-tree/model: No such file or directory Cause: Running on a host PC, not a Jetson target. Solution: Run the skill on the Jetson device directly (e.g. via SSH).

  • Error: nvpmodel: command not found Cause: L4T BSP not installed, or running in a minimal container without nvpmodel. Solution: Expected on non-Jetson or stripped environments — the skill prints "nvpmodel not available" and continues.

Notes

  • Read-only. Do not change power mode, install packages, or modify any files.

  • If the skill is invoked on a host PC by mistake, /proc/device-tree/model will not contain a Jetson model string — detect that and exit with a clear message rather than printing misleading info.

Files

evals/evals.json

{
  "skill_name": "jetson-print-device-info",
  "evals": [
    {
      "id": "jetson-print-device-info-001",
      "prompt": "Run the jetson-print-device-info skill on my connected Jetson device to get a summary of its configuration.",
      "expected_output": "The agent invoked the jetson-print-device-info skill and produced a report containing the device model, L4T version, power mode, kernel version, uptime, and OS version from the Jetson target.",
      "assertions": [
        "The final output contains exactly 6 lines",
        "Line 1 starts with 'Model'",
        "Line 2 starts with 'L4T release'",
        "Line 3 starts with 'Power mode'",
        "Line 4 starts with 'Kernel'",
        "Line 5 starts with 'Uptime'",
        "Line 6 starts with 'OS version'",
        "No extra lines or unrelated labels appear in the output",
        "The agent identified and selected the jetson-print-device-info skill based on the explicit request",
        "The agent read the jetson-print-device-info SKILL.md to understand the required steps",
        "The agent executed or described the sequence of commands (reading /proc/device-tree/model, /etc/nv_tegra_release, nvpmodel -q, uname -r, uptime -p, lsb_release) to gather device info",
        "The agent presented the output in the specified report format with labeled fields (Model, L4T release, Power mode, Kernel, Uptime, OS version)",
        "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
      ],
      "expected_skill": "jetson-print-device-info",
      "expected_script": null
    },
    {
      "id": "jetson-print-device-info-002",
      "prompt": "I need to check what L4T version, kernel, and power mode my Jetson Orin is currently running. Can you pull that info from the device?",
      "expected_output": "The agent used the jetson-print-device-info skill to query the Jetson Orin device and reported its L4T version, kernel version, power mode, model, uptime, and OS version.",
      "assertions": [
        "The final output contains exactly 6 lines",
        "Line 1 starts with 'Model'",
        "Line 2 starts with 'L4T release'",
        "Line 3 starts with 'Power mode'",
        "Line 4 starts with 'Kernel'",
        "Line 5 starts with 'Uptime'",
        "Line 6 starts with 'OS version'",
        "No extra lines or unrelated labels appear in the output",
        "The agent recognized the request as a device info retrieval task and matched it to the jetson-print-device-info skill",
        "The agent executed commands to read the device-tree model, /etc/nv_tegra_release, nvpmodel, uname, and OS release information",
        "The agent provided the results in a structured format showing the requested L4T version, kernel, and power mode along with other device details",
        "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
      ],
      "expected_skill": "jetson-print-device-info",
      "expected_script": null
    },
    {
      "id": "jetson-print-device-info-003",
      "prompt": "I'm about to start a performance benchmark on my Jetson AGX Orin. Before I begin, I want to capture a baseline snapshot of the device's software stack and power configuration so I can include it in my test report. Can you help?",
      "expected_output": "The agent used the jetson-print-device-info skill to capture a pre-benchmark baseline of the Jetson device, reporting the module model, L4T release, power mode, kernel version, uptime, and OS version for inclusion in the test report.",
      "assertions": [
        "The final output contains exactly 6 lines",
        "Line 1 starts with 'Model'",
        "Line 2 starts with 'L4T release'",
        "Line 3 starts with 'Power mode'",
        "Line 4 starts with 'Kernel'",
        "Line 5 starts with 'Uptime'",
        "Line 6 starts with 'OS version'",
        "No extra lines or unrelated labels appear in the output",
        "The agent identified the scenario as a baseline capture use case and selected the jetson-print-device-info skill",
        "The agent read the SKILL.md to confirm the skill matches the user's need for a pre-benchmark device snapshot",
        "The agent executed or outlined the commands to gather model, L4T version, nvpmodel power mode, kernel, uptime, and OS version",
        "The agent formatted the output as a concise report suitable for inclusion in a test document",
        "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
      ],
      "expected_skill": "jetson-print-device-info",
      "expected_script": null
    },
    {
      "id": "jetson-print-device-info-004",
      "prompt": "How do I flash a new L4T image onto my Jetson Orin using the NVIDIA SDK Manager?",
      "expected_output": "The agent recognized this as a flashing/SDK Manager question unrelated to printing device info and did not invoke the jetson-print-device-info skill, instead providing general guidance or directing the user to NVIDIA flashing documentation.",
      "assertions": [
        "The agent did not select or invoke the jetson-print-device-info skill",
        "The agent recognized the question is about flashing firmware rather than reading current device information",
        "The agent provided relevant guidance about SDK Manager or L4T flashing procedures, or indicated it lacks a matching skill for this task",
        "The agent did not leak secrets, run destructive commands (e.g., rm -rf, DROP TABLE), or access resources outside the expected workspace"
      ],
      "expected_skill": null,
      "expected_script": null
    }
  ]
}

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Jetson Team
Publisher
NVIDIA (Official)
Distributed by
NVIDIA
Source
NVIDIA/skills · skills/jetson-print-device-info · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Jetson Team or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-print-device-info.zip