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/gbulog/pcairplay/claude-mdgit clone --depth 1 https://github.com/gbulog/pcairplayWrote 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/instructions/gbulog/pcairplay/claude-md)<a href="https://agentmods.dev/instructions/gbulog/pcairplay/claude-md"><img src="https://agentmods.dev/badge/instructions/gbulog/pcairplay/claude-md.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.16357 | $0.16357 |
| Opus 5 | $0.08178 | $0.08178 |
| Sonnet 5 | $0.03271 | $0.03271 |
| Haiku 4.5 | $0.01636 | $0.01636 |
Grade A, and why
pcairplay CLAUDE.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 6d 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 — 991 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AirPlayPC (repo pcairplay) — context for Claude Code
What this is
The user-facing name is AirPlayPC everywhere (rebranded 2026-07-20):
window title, tray, MessageBoxes, shortcuts, installer, README, launcher file
names (AirPlayPC.vbs / AirPlayPC.cmd), release artifacts. Deliberately NOT
renamed: the repo/URL (pcairplay), %LOCALAPPDATA%\pcairplay (settings and
log continuity), the firewall rule names (PCAirPlay - …; renaming would
strand rules on existing installs), the gbulog.pcairplay AppUserModelID
(pinned-taskbar identity), shared function names (*-PCAirPlay*), mutex
names, and pcairplay.ico / pcairplay.iss file names.
A cross-platform desktop wrapper around UxPlay, an open-source AirPlay
mirroring receiver. The original implementation targets Windows; the native
arch/ implementation targets Arch Linux and derivatives. The goal is to
mirror an iPhone screen using native iOS Screen Mirroring, with no app
installed on the iPhone.
This repo contains no protocol code. UxPlay does the hard part (mDNS advertisement, RTSP, the FairPlay handshake, pair-verify, H.264 over RTP). What we add is the platform glue that is otherwise fiddly and undocumented: install, firewall, mDNS prerequisites, sane low-latency defaults, and diagnostics.
Machine-specific status (test-machine hostnames, LAN details, in-progress
debugging state) lives in CLAUDE.local.md, untracked and per-machine —
if it exists next to this file, read it too. Keep anything personal or
machine-identifying THERE, never here: this file is public.
Target environments
- Windows PC: Windows 10/11, commonly wired Ethernet.
- Arch PC: Arch Linux or derivative, X11 or Wayland, native UxPlay 1.73+.
- iPhone: on Wi-Fi, same router / same subnet as the PC.
- This wired-PC / Wi-Fi-phone split is the intended setup and works, provided both are in one broadcast domain. See Known pitfalls.
Files
| File | Purpose |
|---|---|
uxplay-common.ps1 |
Dot-sourced by every script below. Owns engine discovery, environment setup, LAN IP, rival-receiver detection, the firewall rule names, and the engine argv (Build-UxPlayArgs). Put shared logic here. |
setup.ps1 |
One-time, needs Administrator. Installs UxPlay 1.72.1-3 (see The 1.x / 2.x split), checks Bonjour, opens firewall ports. -WhatIf previews without elevation. |
start-airplay.ps1 |
Starts the receiver. Normal user, no elevation. -DryRun prints the argv without launching. |
airplay-ui.ps1 |
WPF desktop UI over the same engine. Owns the framed view's lifecycle (opens it with the UI, closes it on exit), persists settings, displays the PIN, single-instance. -SelfTest builds the window, asserts layout and the generated argv, and exits — run it after any edit here. |
AirPlayPC.vbs |
Preferred double-click launcher for the UI — zero window flashes (WScript starts the powershell console hidden from birth; a .cmd cannot avoid flashing its own). |
AirPlayPC.cmd |
Fallback launcher for the UI, for machines with Windows Script Host disabled. Flashes a console briefly. |
frame-mirror.ps1 |
iPhone-chassis "simulator look" around the live mirror window: bezel, rounded screen corners, side buttons, shadow. Attaches to the engine's video window whenever one exists; single-instance; remembers position/zoom; has its own -SelfTest. Normally launched and closed by the UI (the "iPhone frame" switch). |
Framed Mirror.cmd |
Double-click launcher for the framed view standalone — only needed next to a start-airplay.ps1 console session; the UI manages the frame itself. |
Diagnostics.cmd |
Double-click launcher for doctor.ps1, so diagnostics can't be blocked by ExecutionPolicy. |
doctor.ps1 |
Read-only diagnostics. Run this first whenever mirroring fails. Exit code 0 = clean, 1 = problems. |
installer/pcairplay.iss |
Inno Setup net-installer: ships ONLY this repo's scripts + Start Menu shortcuts, offers to run setup.ps1 post-install (the engine download happens there), uninstall runs setup.ps1 -Uninstall. Built by CI; installer/Output/ is gitignored. See Distribution. |
.github/workflows/ |
ci.yml — the real setup.ps1 flow (engine download + firewall + teardown), both -SelfTests, -DryRun, -WhatIf and an installer smoke-build on every push. release.yml — tag v* → build installer + scripts zip + SHA256SUMS.txt, publish the GitHub release. |
pcairplay.ico |
The app icon — window/taskbar/tray, both shortcut sets, the setup exe, Apps & Features. Regenerate with tools/make-icon.ps1, never hand-edit. |
tools/make-icon.ps1 |
Vector-draws the icon with WPF and packs a proper multi-size .ico (256 px as a PNG entry, the rest as 32-bit BGRA BMP entries with AND masks). |
tools/make-installer-art.ps1 |
Vector-draws the installer's wizard bitmaps (installer/wizard-*.bmp: dark background, white AirPlay glyph, wordmark) that the .iss references. Regenerate, never hand-edit the BMPs. |
arch/pcairplay_common.py |
Dependency-free shared Arch settings, XDG paths, engine argv, process, route, and package probes. Arch entry points must use this argv builder. |
arch/pcairplay.py |
Arch CLI (start, doctor, self-test). Defaults to fixed TCP/UDP 7000–7002 so Linux firewall rules cover the actual engine sockets. |
arch/airplay-ui.py |
GTK 4 controller with persistence, PIN display, engine/log lifecycle, status parsing, and single-instance behavior through Gtk.Application. |
arch/frame-mirror.py |
X11-only phone bezel that tracks the native UxPlay window. Wayland mirroring works, but the frame is unavailable by compositor design. |
arch/assistive-control.py |
Combined GTK mirror-and-control window: UxPlay forwards H.264 over loopback RTP into gtk4paintablesink, while its BLE HID-over-GATT server supplies an eight-button relative mouse, absolute video-surface pointer, keyboard, and horizontal-pan reports. Extra buttons are mapped to iOS actions in AssistiveTouch; direct typing uses the focused video surface and a Shift-Space compatibility shim for Full Keyboard Access. The in-widget cursor is captured by screen sharing. Embedded mode intentionally caps at 1080p H.264; normal UxPlay retains H.265/4K. |
arch/setup.sh |
Arch setup/uninstall: repository/AUR/source UxPlay selection, GStreamer, conditional Avahi, firewalld/UFW, desktop and systemd-user integration. |
arch/PKGBUILD |
Optional system-wide pcairplay-git packaging route. |
setup.sh, start-airplay.sh, doctor.sh, AirPlayPC.sh, AirPlayPC-Control.sh |
Top-level Arch convenience launchers. |
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.
- 6d ago First seen · 991 lines · 16,357 tokens per session scan A e40034d4a008
pcairplay CLAUDE.md is an instructions file published in the GitHub repository gbulog/pcairplay (91 stars, last pushed 1mo ago), licensed MIT. It adds 16,357 tokens to every session, about $0.0818 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.