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-developgit 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-develop)<a href="https://agentmods.dev/skills/folotoy/ai-passport/passport-develop"><img src="https://agentmods.dev/badge/skills/folotoy/ai-passport/passport-develop/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-develop"><img src="https://agentmods.dev/badge/skills/folotoy/ai-passport/passport-develop.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.00043 | $0.00948 |
| Opus 5.5 | $0.00017 | $0.00379 |
| Sonnet 5.5 | $0.00009 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
passport-develop 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop an AI Passport Application
Use this workflow for an implementation request, not as permission to start a
different project. The user's explicit choices take precedence over this
skill's defaults. Resolve the target checkout with git rev-parse --show-toplevel;
all paths below are relative to that checkout, not the installed skill folder.
Read AGENTS.md and docs/development/ai-guide.md, then only the task's routed
documents. Start with git status --short --branch.
Turn the request into a working increment
- Establish the intended behavior and acceptance checks: screens, three-button actions, persistent data, networking/audio, and failure states as relevant. Ask only questions that materially affect the implementation; state reasonable defaults. Do not add Wi-Fi, cloud services, new wiring, or paid dependencies to an offline request. Missing hardware facts are not assumptions to invent.
- Continue an existing application on its intended branch. For a new application,
start from the agreed baseline on
feature/*, preserving dirty work. Do not switch, stash, reset, or overwrite someone else's changes to obtain a clean starting point. If work overlaps or branch choice is ambiguous, resolve it with the user. Do not commit, push, or publish without authorization. - Consult relevant demo branches and
docs/reference/README.md. Extract the needed patterns, not whole branches or their stale BSP/configuration. Apply the AI guide's mandatory UI redesign rule: derivative applications must have their own screens and interactions, never the current demo test menu, screens, or visual shell. Renaming or recoloring that shell is not a redesign. Reuse BSP APIs and isolated logic; do not rewrite drivers just to change the UI. - Implement the smallest complete behavior with tests for pure logic. Keep
application state/tasks in
mainand reuse the BSP. Apply the existing LVGL locking, callback, teardown, RAM, and configurable-partition rules. Consult the Chinese-font or Wi-Fi provisioning guide only when the feature needs it. - Run focused tests while editing and the complete repository gate before delivery. Repair failures caused by the change; do not suppress checks or sweep unrelated failures into the task. Report environmental blockers with their evidence and the remaining actionable step.
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 · 75 lines · 43 tokens per session scan A 43fd1f4e2605
passport-develop is a skill published in the GitHub repository FoloToy/ai-passport (646 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 948 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.