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/mjmirza/app-store-complianceWrote 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/mjmirza/app-store-compliance/app-store-audit)<a href="https://agentmods.dev/commands/mjmirza/app-store-compliance/app-store-audit"><img src="https://agentmods.dev/badge/commands/mjmirza/app-store-compliance/app-store-audit/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/mjmirza/app-store-compliance/app-store-audit"><img src="https://agentmods.dev/badge/commands/mjmirza/app-store-compliance/app-store-audit.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.00035 | $0.00984 |
| Opus 5 | $0.00017 | $0.00492 |
| Sonnet 5 | $0.00007 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
app-store-audit scanned grade A with 1 finding 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 10d 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.
Enumerates other installed skillslowAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
5. If the app was already rejected, find the matching pattern in `~/.claude/skills/app-store-compliance/data/rejection-patterns.json`, apply the fix, then follow the appeal playbook in the docs. Never resubmit an unchang Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago First seen · 47 lines · 35 tokens per session scan A 4954512ee3bf
app-store-audit is a command published in the GitHub repository mjmirza/app-store-compliance (208 stars, last pushed yesterday), with no licence file. It adds 35 tokens to every session and 984 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
audit
Scan a codebase for existing observability instrumentation and identify gaps.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
feature-learn
View and manage patterns learned from feature builds. Shows extracted instincts, confidence scores, and feature completeness history.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-plan
Plan a mobile feature with architecture decisions, file breakdown, dependency analysis, and test strategy. Produces a structured plan document reviewed by an architecture agent.
feature-implement
Implement a planned mobile feature using parallel specialized agents for network, data, architecture, UI, and wiring layers. Requires an approved feature plan.