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 instructions/jvgomg/podkit/agents-mdgit 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.04980 | $0.04980 |
| Opus 5 | $0.02490 | $0.02490 |
| Sonnet 5 | $0.00996 | $0.00996 |
| Haiku 4.5 | $0.00498 | $0.00498 |
Grade A, and why
podkit AGENTS.md 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 today.
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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents (Claude Code, Cursor, etc.) working in this repository.
Project Summary
podkit is a TypeScript toolkit for syncing music collections to iPod devices. It provides a CLI and library that handles collection diffing, transcoding (FLAC→AAC), metadata preservation, and artwork transfer.
Status: Active development
Monorepo structure:
packages/ # Published / published-adjacent packages
├── compatibility/ # Cross-version compatibility helpers
├── demo/ # Animated GIF demo (VHS + mocked CLI build)
├── device-types/ # Shared TypeScript types for device capabilities, identity, firmware
├── devices-ipod/ # Pure TypeScript iPod generation tables + capability synthesis (no libgpod)
├── devices-mass-storage/ # User-extensible mass-storage preset framework (Echo Mini, Rockbox, generic)
├── docs-site/ # Documentation site (Starlight/Astro)
├── ipod-avatar/ # iPod avatar image assets
├── ipod-db/ # Pure TypeScript iTunesDB/ArtworkDB parser (browser-compatible)
├── ipod-firmware/ # iPod firmware inquiry — SCSI via koffi (SG_IO/IOKit), USB via the `usb` npm package
├── ipod-web/ # Virtual iPod UI — React + Jotai web component
├── libgpod-node/ # Native Node.js bindings for libgpod (database operations only; no USB/libusb)
├── podkit-core/ # Core sync logic, adapters, transcoding
├── podkit-cli/ # Command-line interface
├── podkit-docker/ # Docker image (Dockerfile, entrypoint, compose files)
├── podkit-daemon/ # Background sync daemon
├── virtual-ipod-app/ # Tauri macOS app — frameless iPod-shaped window
└── virtual-ipod-server/ # Lima VM backend — USB gadget + REST/WebSocket API
test-packages/ # Testing infrastructure (private, not published)
├── device-testing/ # VM test harness — DevicePersona + SystemState registries, TestRuntime, Lima yamls, apply-state.sh
├── device-testing-daemon/ # Userspace daemon — synthesises iPod USB gadgets (FunctionFS + mass-storage) on dummy_hcd
├── e2e-tests/ # End-to-end CLI tests on the host (dummy + real iPod). Docker-gated files live in the `src/docker-source/` surface dir
├── e2e-shared/ # Cross-cutting helpers shared by every e2e package (CLI runner, preflight, error assertions)
├── e2e-vm-tests/ # End-to-end podkit feature tests inside the Lima VM
├── gpod-testing/ # Test utilities for iPod environments (no hardware needed)
└── test-fixtures/ # Static + dynamic test fixtures (audio + video, lib + CLI generators)
tools/
├── demo/ # Live demo documentation for the virtual iPod system
├── gpod-tool/ # C CLI for iPod database operations
├── libgpod-macos/ # macOS build scripts for libgpod
└── lima/ # Lima VM configs (Debian, Alpine, virtual-ipod)
devices/ # Device documentation profiles (specs, capabilities, research)
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.
- today First seen · 343 lines · 4,980 tokens per session scan A f9b1dee38a9c
podkit AGENTS.md is an instructions file published in the GitHub repository jvgomg/podkit (39 stars, last pushed 9d ago), licensed MIT. It adds 4,980 tokens to every session, about $0.0249 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-09-01.
Other instructions, from other repositories
librosa AGENTS.md
Instructions for librosa/librosa, covering agent interaction policy for librosa, 1. automated platform interactions, 2. exception for project-authorized automation and 3. machine-readable directive.
spotatui copilot-instructions.md
Instructions for LargeModGames/spotatui, covering copilot instructions for spotatui, build & run, ci checks (run before opening a pr), run a single test and example.
musicbox AGENTS.md
Instructions for darknessomi/musicbox, covering agents.md, cursor cloud specific instructions, running the app, audio backends (system deps, not in update script) and network / api note.
nuclear AGENTS.md
AGENTS.md instructions for nukeop/nuclear, covering agents.md, project overview, packages, commands and development.
nuclear copilot-instructions.md
Copilot instructions for nukeop/nuclear, covering nuclear music player - copilot instructions, project overview, key features, tech stack and packages.
pytheory CLAUDE.md
Instructions for kennethreitz/pytheory, covering claude code instructions, release process, version bumping, testing and publishing.