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/modem-dev/podguy/agents-mdgit clone --depth 1 https://github.com/modem-dev/podguyWhat 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.01029 | $0.01029 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
podguy 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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
podguy project instructions
This repository is primarily operated through pi for podcast post-production work.
Default to the podguy-post-production workflow unless the user explicitly asks for something else. Use podguy-clip-cutter when the user asks to export or cut social clips. Use podguy-youtube-publisher when the user asks to upload, schedule, or manage episodes on YouTube.
Primary tasks
- scan episode videos for likely interstitials and non-host inserts when video is available
- generate transcripts for draft, preview, or final episode exports
- derive YouTube/podcast chapters in timestamp-title format
- give editorial feedback such as cuts, highlights, weak sections, and insert opportunities
- cut selected highlight moments into review exports for TikTok, Reels, YouTube Shorts, trailers, or social posts
- draft publishing assets such as show notes, quote sheets, and proper noun review
- upload finished episodes to YouTube with metadata composed from analysis artifacts
Podcast profile
- Prefer show-specific settings from
podguy.tomlwhen present. - Use
podguy.example.tomlas the template for new shows. - Do not assume a specific show, hosts, audience, tone, or episode naming convention unless the profile or user provides it.
Working guidance
- prefer writing generated outputs under
dist/analysis/ - reuse existing analysis outputs when they already match the requested episode/version
- treat scanner results as heuristic review aids, not exact edit points
- support audio-only files, video drafts, preview exports, and final renders
- skip the visual scanner for audio-only inputs and on non-macOS systems (it requires Swift/AVFoundation); say why when skipping
- use transcript evidence and timecodes whenever possible when giving editorial feedback
- treat generated clip media as review exports, not final mastered social edits
- never upload to YouTube without explicit user confirmation of the final metadata; default uploads to private
- use
scripts/download_sample_media.shwhen a real open-license video-podcast sample is helpful; keep downloaded samples under gitignoreddist/
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.
- 2d ago First seen · 103 lines · 1,029 tokens per session scan A 37d2d72c281b
podguy AGENTS.md is an instructions file published in the GitHub repository modem-dev/podguy (46 stars, last pushed 16d ago), licensed MIT. It adds 1,029 tokens to every session, about $0.0051 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
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.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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
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.
langchain 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.