alwaysai-setup

alwaysai-setup is a skill for Claude Code, Codex from Seeed-Projects/Seeed-Jetson-DevelopTool. It costs 48 tokens per session (990 once invoked), scanned B, original, MIT.

A setup procedure for running object-detection models on NVIDIA Jetson devices with alwaysAI. Object detection is computer vision that identifies and locates things in camera images or video; TensorRT helps optimize models for NVIDIA hardware.

In plain words
What is it for?
Use it to configure alwaysAI, connect a supported Jetson device, and run object detection on live camera feeds or video files.
Why use it?
It checks the required JetPack version, camera, host tools, and SSH connection before deployment. This reduces setup errors when moving an alwaysAI project from a computer to a Jetson.

Skill for Claude CodeCodex

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 skills/seeed-projects/seeed-jetson-developtool/alwaysai-setup
Any agent
npx skills add Seeed-Projects/Seeed-Jetson-DevelopTool --skill alwaysai-setup
Clone the repo
git clone --depth 1 https://github.com/Seeed-Projects/Seeed-Jetson-DevelopTool

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for alwaysai-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/alwaysai-setup.svg)](https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/alwaysai-setup)
Your own site
<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/alwaysai-setup"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/alwaysai-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 990 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00048 $0.00990
Opus 5 $0.00024 $0.00495
Sonnet 5 $0.00010 $0.00198
Haiku 4.5 $0.00005 $0.00099

Measured 4d ago against content hash 3d54ff1bb560, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

alwaysai-setup scanned grade B 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 4d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo apt-cache show nvidia-jetpack
seeed_jetson_develop/skills/openclaw/alwaysai-setup/SKILL.md · 146 lines

How it starts

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

alwaysAI on NVIDIA Jetson

alwaysAI is a computer vision development platform for creating and deploying ML applications on edge devices. Deploy object detection projects from a host PC to Jetson via SSH, with TensorRT-optimized models for real-time inference.

Hardware: Jetson device (Nano/Xavier NX/AGX Xavier/AGX Orin), USB webcam or MIPI CSI camera Software: JetPack 4.6 with all SDK components, host PC (Windows/Linux/Mac)


Execution model

Run one phase at a time. After each phase:

  • If output contains [STOP] → stop immediately, consult the failure decision tree
  • If output ends with [OK] → tell the user "Phase N complete" and proceed

Phase 1 — prerequisites check (~30 s)

On Jetson:

sudo apt-cache show nvidia-jetpack
# Confirm JetPack 4.6
ls /dev/video*
# Confirm camera is connected

[OK] when JetPack 4.6 confirmed and camera detected.


Phase 2 — setup host PC (~5 min)

On the development PC:

  1. Download and install alwaysAI from https://alwaysai.co/installer/windows (or Mac/Linux equivalent)
  2. Verify CLI:
aai -v
  1. Verify OpenSSH:
ssh -V

[OK] when aai and ssh both return version numbers.


Phase 3 — setup Jetson environment (~2 min)

On Jetson:

sudo usermod -aG docker $USER

Log out and back in, then verify:

docker run hello-world

[OK] when hello-world runs without sudo.


Phase 4 — create account & project (human action)

  1. Sign up at https://console.alwaysai.co/auth?register=true
  2. Create a new project: Dashboard → New Project → Object Detection
  3. Delete the default mobilenet_ssd model (not optimized for Jetson)
  4. Add optimized model: Model Catalog → search ssd_mobilenet_v1_coco_2018_01_28_xavier_nx → Add To Project

[OK] when project has the TensorRT-optimized model.


Phase 5 — deploy to Jetson (~5 min)

On host PC, create a project folder and configure:

mkdir ~/alwaysai-project && cd ~/alwaysai-project
aai app configure

Read the full file on GitHub · 146 lines

Files

What ships with it

2 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.

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. 4d ago First seen · 146 lines · 48 tokens per session scan B 3d54ff1bb560

Subscribe to this mod's changes

alwaysai-setup is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 990 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens