device-info

device-info is a command for coding agents from phinn/KinetAios. It costs 22 tokens per session (331 once invoked), scanned A, original, GPL-3.0.

A device-scanning command that identifies the connected chip and its VID:PID hardware identifiers. It also provides suggestions for the driver needed to use the device.

In plain words
What is it for?
Use it when diagnosing an attached device, identifying its chip model, checking its USB identifiers, or deciding which driver to try.
Why use it?
It reduces the manual work of finding out what hardware is connected and which driver may support it.

Command

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 commands/phinn/kinetaios/device-info
Clone the repo
git clone --depth 1 https://github.com/phinn/KinetAios

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 device-info

README.md
[![agentmods](https://agentmods.dev/badge/commands/phinn/kinetaios/device-info.svg)](https://agentmods.dev/commands/phinn/kinetaios/device-info)
Your own site
<a href="https://agentmods.dev/commands/phinn/kinetaios/device-info"><img src="https://agentmods.dev/badge/commands/phinn/kinetaios/device-info.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00022 $0.00331
Opus 5 $0.00011 $0.00166
Sonnet 5 $0.00004 $0.00066
Haiku 4.5 $0.00002 $0.00033

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

Security

Grade A, and why

device-info 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 5d 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.

plugins/serial-comm/commands/device-info.md · 36 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 5d ago First seen · 36 lines · 22 tokens per session scan A e257f13d43fe

Subscribe to this mod's changes

device-info is a command published in the GitHub repository phinn/KinetAios (8 stars, last pushed yesterday), licensed GPL-3.0. It adds 22 tokens to every session and 331 once invoked, about $0.0001 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-08-31.