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 skills add FoloToy/ai-passport --skill passport-setupgit clone --depth 1 https://github.com/FoloToy/ai-passportWrote 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/folotoy/ai-passport/passport-setup)<a href="https://agentmods.dev/skills/folotoy/ai-passport/passport-setup"><img src="https://agentmods.dev/badge/skills/folotoy/ai-passport/passport-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/folotoy/ai-passport/passport-setup"><img src="https://agentmods.dev/badge/skills/folotoy/ai-passport/passport-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.00683 |
| Opus 5.5 | $0.00016 | $0.00273 |
| Sonnet 5.5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
passport-setup 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare the Development Environment
Resolve the target checkout and read its AGENTS.md and
docs/development/engineering/environment-setup.md. Paths refer to that
checkout. Preserve the user's chosen OS, installation paths, proxies, and
existing tools; do not replace another ESP-IDF installation.
Inspect before changing anything
- Run
git status --short --branch; identify OS, architecture, shell, and whether execution is local, WSL, a VM, container, or remote agent. - Check the active
idf.py --versionand the selected installation. An inactive shell is not proof the toolchain needs reinstalling. Activate an existing ESP-IDF 5.5.3 in the current shell when available. - Check the build prerequisites and dependency lock before downloading tools. Do not print complete environment variables or authentication configuration.
- Discover USB/serial access without opening ports when relevant to the user's request. Separate build readiness from access to the user's physical device.
Repair the smallest demonstrated problem
Follow the environment guide's matching platform and download route. Explain the proposed installation or configuration change and obtain the approvals required by the environment before system-package installation, network access, USB forwarding, group changes, or writes outside the workspace. Do not disable TLS verification, antivirus, or other security controls to make setup pass.
Do not run destructive recovery recipes, remove tool caches/checkouts, or edit global Git/shell settings as routine setup. Preserve partial/user installations; if a repair would remove or replace material, identify exact targets and ask first. After a retry, inspect the new evidence instead of repeating the same failed operation indefinitely. If progress needs access or a user choice, stop that operation and report the blocker; continue independent safe checks.
Require the selected environment to report ESP-IDF 5.5.3 before generating
configuration. Preserve intentional sdkconfig and partition changes. On
native Windows, use the documented ESP-IDF terminal; the repository's shell
gate also needs a compatible shell environment. Do not treat POSIX commands as
PowerShell commands or promise WSL automatically has USB access.
What ships with it
1 file 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.
- 1mo ago First seen · 61 lines · 41 tokens per session scan A 7ec54376c728
passport-setup is a skill published in the GitHub repository FoloToy/ai-passport (646 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 683 once invoked, about $0.0002 per session on Opus 5.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-09-17.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.