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 pockebot/openpocket --skill human-auth-nfcgit clone --depth 1 https://github.com/pockebot/openpocketWrote 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/pockebot/openpocket/human-auth-nfc)<a href="https://agentmods.dev/skills/pockebot/openpocket/human-auth-nfc"><img src="https://agentmods.dev/badge/skills/pockebot/openpocket/human-auth-nfc.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.1 | $0.00031 | $0.00576 |
| Opus 5 | $0.00015 | $0.00288 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
human-auth-nfc 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human Auth: NFC / RFID
Use this when an app requires NFC (Near Field Communication) or RFID interaction that the emulator cannot perform.
When to Trigger
- App asks user to "Tap your card" or "Hold your phone near the reader".
- App needs to read an NFC tag (transit card, access badge, smart tag).
- App requires contactless payment confirmation.
- Any flow requiring physical NFC/RFID interaction.
How to Call
request_human_auth(
capability: "nfc",
instruction: "Please tap your [card/tag/device] to read NFC data for [purpose].",
uiTemplate: {
allowTextAttachment: true,
allowFileAttachment: true,
title: "NFC / RFID Tap Required",
summary: "Tap your NFC card or tag and provide the result."
}
)
What You Receive
- If the human entered the NFC data as text:
artifact_kind: text,value: "<nfc_data>" - If the human provided a file dump:
artifact_type: application/octet-streamor similar
How to Apply
NFC data application depends heavily on the app's expected input:
Transit / Access Card ID
- Read the artifact to get the card UID or data.
- If the app has a manual entry option, type the card ID.
- If no manual entry exists, the flow may require the human to use Remote Takeover to complete the NFC step directly.
NFC Tag Content (URL, text record)
- Read the artifact text content.
- If it's a URL, open it:
shell("am start -a android.intent.action.VIEW -d '<url>'") - If it's text data, type it into the relevant app field.
Contactless Payment
NFC payment typically cannot be delegated — it requires the physical card/phone at the terminal. In this case:
- Inform the user via the decision note that this step requires physical presence.
- The human completes the payment on their end.
- Approve without artifact if the payment was completed externally.
Limitations
- Emulators have no NFC hardware. NFC interactions always require human delegation.
- Some NFC operations are one-shot (e.g., transit gate) and cannot be replayed.
- Real-device Agent Phones may have NFC but cannot proxy another phone's secure element.
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.
- 7d ago First seen · 63 lines · 31 tokens per session scan A f3ba5ce1ba76
human-auth-nfc is a skill published in the GitHub repository pockebot/openpocket (841 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 576 once invoked, about $0.0002 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-30.
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.
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…
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…
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.