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/abdullah4ai/apple-developer-toolkit/agents-mdgit clone --depth 1 https://github.com/Abdullah4AI/apple-developer-toolkitWhat 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.00728 | $0.00728 |
| Opus 5 | $0.00364 | $0.00364 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
apple-developer-toolkit 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Engineering Rules
This repository is updated from upstream on a recurring cadence. After every upstream sync, preserve or reapply the project-level agent rules below.
Core Principles
- Do not let temporary run state poison future agent behavior.
- Make tool permissions explicit before side effects.
- Keep observability artifacts for non-trivial runs.
- Route workflows through the right surface instead of guessing.
Memory Discipline
- Do not persist task logs, raw Apple docs output, generated code snippets, App Store state, build errors, credentials, or temporary decisions as long-term memory.
- Save only stable reusable facts: durable user preferences, environment conventions, tool quirks, or confirmed setup details.
- Prefer repo artifacts, run summaries, status files, and skill references for workflow state.
Tool Permission Design
Read-only by default:
node cli.js search,symbols,doc,overview,samples, andwwdc-*appledev store ... list/status/validate/diff/docs/doctor- Reading reference files, README files, config defaults, and docs
Requires explicit user approval before side effects:
- App Store Connect creates, updates, deletes, uploads, TestFlight publish, App Store submit, pricing, IAP, subscriptions, certificates, profiles, devices, webhooks, notarization, and Xcode Cloud runs
appledev buildactions that write a local project, fix files, launch simulators, install hooks, or invoke credentials- Any GitHub write action: commits, pushes, PR creation, merges, releases, tags, or workflow changes
Never use this repository or skill to post to X/Twitter or invoke any X publishing command.
Observability Requirements
For non-trivial runs, leave enough audit trail to understand what happened:
- Logs: preserve relevant command output or failure excerpts.
- Traces: state which surface was used:
node cli.js,appledev store, orappledev build. - Artifacts: write plans, diffs, reports, metadata exports, or build summaries to project-local files when appropriate.
- Status files: for long release or app-builder workflows, keep a compact status summary with current step, target app/project, next safe action, and blockers.
- Run summaries: finish with what was checked, what changed, what did not change, and remaining risks.
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 · 69 lines · 728 tokens per session scan A ac182c28572c
apple-developer-toolkit AGENTS.md is an instructions file published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed 4d ago), licensed MIT. It adds 728 tokens to every session, about $0.0036 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.
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.