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 agents/jvgomg/podkit/ipod-firmwaregit clone --depth 1 https://github.com/jvgomg/podkitWhat 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.00000 | $0.01237 |
| Opus 5 | $0.00000 | $0.00619 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
ipod-firmware 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 yesterday.
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.
@podkit/ipod-firmware
iPod firmware inquiry — SCSI (SG_IO/IOKit via koffi) and USB (control transfer via the usb npm package).
Read this when working on:
- The inquiry orchestrator, transport selection, or probe.
- The diagnostic logger surface.
- Bundling
@podkit/ipod-firmware(or anything that depends on it transitively) into a single-file binary.
Diagnostic logging
The library does not write to stderr/stdout. It exposes setLogger(fn | null) and emits structured FirmwareLogEvents through it. Default is no-op.
import { setLogger } from '@podkit/ipod-firmware';
setLogger((event) => {
process.stderr.write(`[${event.level}] ${event.message}\n`);
});
The CLI installs a logger in its preAction hook when -v is passed; library code stays platform/UI-agnostic. If you build another consumer (Tauri app, daemon, etc.) and want diagnostic output, install your own receiver.
Bundling into a single-file binary
@podkit/ipod-firmware depends on the usb npm package, which uses node-gyp-build to load a per-platform prebuilt .node from node_modules/usb/prebuilds/ at runtime. Bundlers like Bun --compile can't reach that path inside a compiled binary, so consumers must do two things:
1. Build-time: stage the prebuild
Detect the build host's platform/arch and copy the matching file out of node_modules/usb/prebuilds/ into your bundle's working directory:
| Platform / arch | Prebuild path inside usb package |
|---|---|
| darwin (any arch) | prebuilds/darwin-x64+arm64/node.napi.node |
| linux x64 (glibc) | prebuilds/linux-x64/node.napi.glibc.node |
| linux x64 (musl) | prebuilds/linux-x64/node.napi.musl.node |
| linux arm64 (any libc) | prebuilds/linux-arm64/node.napi.armv8.node |
Only linux-x64 ships separate glibc/musl prebuilds. linux-arm64 ships a single ABI-tagged file (node.napi.armv8.node) that works on both glibc and musl — so don't try to detect libc on arm64. See packages/podkit-cli/scripts/compile.sh for a working example. musl detection on Linux x64 uses ldd /bin/sh | grep -q musl.
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.
- yesterday First seen · 75 lines · 0 tokens per session scan A 0ac48e9ea6b2
ipod-firmware is an agent published in the GitHub repository jvgomg/podkit (39 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,237 tokens. 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-01.
Other agents, from other repositories
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
cline
Cline is an autonomous coding agent for VS Code (and a CLI). It speaks MCP over stdio and HTTP.
neuron-nki-agent
Unified NKI kernel development agent. CRITICAL: Before writing any NKI code, read the language constraint reference at skills/neuron-nki-writing/references/nki-language-constraint.md for the required API patterns and reference kernel template. Context: Kernel won't compile user: "Fix these compilation errors in my…
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…
aemb-builder
你是 auto-embedded 的 Builder。本工程由 RIPER-5 + 项目级 spec 驱动。.
firmware
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for embedded / IoT firmware and devices (firmware image extraction, hardcoded credentials & secrets, backdoors, embedded web/CGI/LuCI interfaces, insecure network services, outdated components — OpenWrt/BusyBox/Dropbear/uhttpd class devices).