Borrowing it
Nothing to install: this file belongs to guitaripod/wwdc-sessions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/guitaripod/wwdc-sessions/master/AGENTS.mdgit clone --depth 1 https://github.com/guitaripod/wwdc-sessionsWrote 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/guitaripod/wwdc-sessions/agents-md)<a href="https://agentmods.dev/instructions/guitaripod/wwdc-sessions/agents-md"><img src="https://agentmods.dev/badge/instructions/guitaripod/wwdc-sessions/agents-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.01264 | $0.01264 |
| Opus 5 | $0.00632 | $0.00632 |
| Sonnet 5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
wwdc-sessions 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.
Agent Guide
A knowledge base of Apple WWDC developer sessions (WWDC 2014-2026, plus Tech Talks and Meet with Apple), structured for direct consumption by AI agents. Free, non-commercial, and complementary to Apple's official material — every session links back to developer.apple.com.
1652 sessions · 1567 transcripts · 15 events · 19 topics.
Layout
catalog.json Master index — START HERE. Provenance, counts, rawBase, every session.
events.json Per-event summaries and counts.
topics.json Topic -> sessions (id, path, title) across all years.
llms.txt llms.txt-format index.
schema/ JSON Schema for catalog, session, events, topics, transcript.
sessions/<event>/<n>-<title-slug>/
metadata.json Structured: platforms, topics, keywords, code snippets,
resources (with sosumi.ai + DocC endpoints), media, languages.
README.md Rendered page with YAML frontmatter.
transcript.md Timecoded transcript prose (when available).
transcript.json { id, language, source, wordCount, segments:[{start, text}] }.
events/<event>/index.md Per-event sessions grouped by topic.
events/<event>/index.json Per-event machine slice (full records) — fetch one year without the full catalog.
topics/<slug>.md Per-topic index across events.
platforms/<slug>.md Per-platform index.
Locating a session — do not derive paths from the id
Every catalog/events record carries an exact relative path (e.g.
sessions/wwdc2026/298-meet-the-evaluations-framework/); the leaf is <eventContentId>-<title-slug>.
To fetch a file, join the catalog's rawBase with path + filename:
<rawBase>/<path>metadata.json
<rawBase>/<path>transcript.json
metadata.json also carries a files map with every relative file path. The numeric prefix of the
leaf is Apple's stable session id, mirroring the video URL developer.apple.com/videos/play/<event>/<n>.
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 Changed cc9c861b67cd
- 7d ago First seen · 103 lines · 1,264 tokens per session scan A 6a9e90cbf1c7
wwdc-sessions AGENTS.md is an instructions file published in the GitHub repository guitaripod/wwdc-sessions (5 stars, last pushed 5d ago), licensed MIT. It adds 1,264 tokens to every session, about $0.0063 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-31.
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.
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).
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.
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.