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 agentmods add skills/seeed-projects/seeed-jetson-developtool/allxon-setupnpx skills add Seeed-Projects/Seeed-Jetson-DevelopTool --skill allxon-setupgit clone --depth 1 https://github.com/Seeed-Projects/Seeed-Jetson-DevelopToolWrote 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/seeed-projects/seeed-jetson-developtool/allxon-setup)<a href="https://agentmods.dev/skills/seeed-projects/seeed-jetson-developtool/allxon-setup"><img src="https://agentmods.dev/badge/skills/seeed-projects/seeed-jetson-developtool/allxon-setup.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00798 |
| Opus 5 | $0.00019 | $0.00399 |
| Sonnet 5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade D, and why
allxon-setup scanned grade D with 3 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 3d 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 wget -qO - "https://get.allxon.net/linux/standard" | sudo bash -s Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
sudo wget -qO - "https://get.allxon.net/linux/standard" | sudo bash -s Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sudo wget -qO - "https://get.allxon.net/linux/standard" | sudo bash -s How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Allxon DMS Setup on Jetson
Allxon is an edge device management solution for remote monitoring and management of Jetson devices via a cloud portal. Installation is a single command.
Hardware: Any NVIDIA Jetson device, OOB Enabler (optional for out-of-band management) Software: JetPack 4.6+, internet connection
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)
cat /etc/nv_tegra_release
Confirm JetPack 4.6 or later. Check internet:
ping -c 2 get.allxon.net
[OK] when JetPack version confirmed and internet works.
[STOP] if JetPack < 4.6 or no internet.
Phase 2 — create Allxon account (human action)
Ask the user: "Do you already have an Allxon DMS account?"
If no:
- Sign up at: https://dms.allxon.com/next/signup
- Verify account via activation email
- Create a password
[OK] when user confirms they have an account.
Phase 3 — install Allxon DMS agent (~2 min)
sudo wget -qO - "https://get.allxon.net/linux/standard" | sudo bash -s
During installation, it will ask whether to install Trend Micro IoT Security (3-month free trial). User can choose Y or N.
Verify agent is running:
systemctl status allxon-dms-agent
[OK] when agent is active/running.
Phase 4 — get pairing code (~30 s)
CLI method:
dms-get-pairing-code
Or GUI method: press Ctrl + Shift + B on the Jetson desktop to open the agent window,
then click "Get device pairing code".
[OK] when pairing code is obtained.
Phase 5 — pair device with portal (~1 min)
- Login to https://dms.allxon.com/next/signin
- Click Devices → + Add Device
- Enter the pairing code from Phase 4
- Click Next to complete pairing
[OK] when device appears in the Allxon DMS Portal.
Failure decision tree
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.
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.
- 3d ago First seen · 120 lines · 38 tokens per session scan D a7b7054777b8
allxon-setup is a skill published in the GitHub repository Seeed-Projects/Seeed-Jetson-DevelopTool (54 stars, last pushed 4d ago), licensed MIT. It adds 38 tokens to every session and 798 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
manage-vast-gpu-fleet
Inspect, price, canary, replace, and document Pollinations-operated Vast.ai GPU workers. Use for scheduled Vast offer scouting, GPU fleet cost or utilization reviews, preparing an isolated replacement, human-approved production cutovers, retiring replaced instances, and the follow-up repository PR.
doca-bf3-deployment
Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with bfb-install from the host, the host-to-DPU TMFIFO management channel (tmfifonet0, the 192.168.100.x convention), RShim daemon state and console-over-rshim, DPU mode…
doca-bf4-deployment
WARNING: guides potentially IRREVERSIBLE BlueField-4 hardware operations (PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets) that can brick firmware, corrupt boot media, or cause outages — a maintenance window and rollback plan are required, and every mutating step is governed by…
doca-container-deployment
Use this skill when the user is hands-on deploying an in-bundle DOCA service container (Argus, DMS, Firefly, or UROM service) on a BlueField — kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness, smoke-before-bulk, and the layered…
unifi-network
How to manage UniFi network infrastructure — devices, clients, firewall, VPN, routing, WLANs, Traffic Flows, and statistics. Use this skill when the user mentions UniFi, Ubiquiti, network management, WiFi configuration, firewall rules, port forwarding, VPN, QoS, bandwidth, traffic flows, connected clients, network…
scan-gke-clusters
Refresh the GKE TPU cluster inventory for one or more GCP projects. Runs .claude/scripts/scan-gke-clusters.sh to enumerate clusters with TPUs in each project (status, XPK presence, ready-node count, XPK type, topology, machine type), writes a per-project Markdown summary at .env/ -gke-tpu-cluster-scan.md, and merges…