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.
git clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsWrote 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/commands/markdavidgan/apple-dev-skills/rejection-recovery)<a href="https://agentmods.dev/commands/markdavidgan/apple-dev-skills/rejection-recovery"><img src="https://agentmods.dev/badge/commands/markdavidgan/apple-dev-skills/rejection-recovery/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/markdavidgan/apple-dev-skills/rejection-recovery"><img src="https://agentmods.dev/badge/commands/markdavidgan/apple-dev-skills/rejection-recovery.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00110 |
| Opus 5 | $0.00009 | $0.00055 |
| Sonnet 5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
rejection-recovery 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 9d 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.
What it actually says
Run the app-rejection-recovery skill on $ARGUMENTS.
Triages an App Store rejection: maps the cited guideline to its bucket and typical fix, drafts a Resolution Center reply, and decides fix-vs-appeal (and whether to request expedited review). Pulls submission/review state via the App Store Connect MCP when available. Hand off prevention to preflight.
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.
- 9d ago First seen · 9 lines · 18 tokens per session scan A b05cb91e536f
rejection-recovery is a command published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 110 once invoked, about $0.0001 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 commands, from other repositories
contract-review-checklist
Extract the terms that matter from an agreement and flag deviations for a lawyer, without giving legal advice.
review-data-privacy
Review a feature for privacy: what is collected, where it goes, how long it stays, and whether deletion works.
agent-build-feature
A strict brief that makes a coding agent implement a feature end to end, matching the codebase and verifying it works.
agent-system-prompt
Write a system prompt for an AI agent that defines its role, tools, boundaries, and output clearly enough to act reliably.
add-code-comments
Add docstrings and comments that explain why, matching the code's existing style, without noise.
break-down-task
Break a goal into an ordered, actionable plan with dependencies and a clear first step.