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 skills/moasq/ios-dev-agent/asc-metadata-yamlnpx skills add moasq/ios-dev-agent --skill asc-metadata-yamlgit clone --depth 1 https://github.com/moasq/ios-dev-agentWrote 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/skills/moasq/ios-dev-agent/asc-metadata-yaml)<a href="https://agentmods.dev/skills/moasq/ios-dev-agent/asc-metadata-yaml"><img src="https://agentmods.dev/badge/skills/moasq/ios-dev-agent/asc-metadata-yaml.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.00165 | $0.01594 |
| Opus 5 | $0.00082 | $0.00797 |
| Sonnet 5 | $0.00033 | $0.00319 |
| Haiku 4.5 | $0.00016 | $0.00159 |
Grade A, and why
asc-metadata-yaml 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 6d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store metadata (YAML source of truth)
All App Store Connect metadata for this app is declared in sectioned YAML under ./metadata/. Treat these files as the authoritative pre-population — App Store Connect is a downstream projection of this directory, never the reverse.
Why this exists
Populating App Store Connect manually on every release leaks state, wastes time, and loses locale parity. This skill replaces guessing with a versioned, reviewable pre-population:
- Every ASC field has a canonical home — one YAML file per ASC section.
- Every file tracks its own
_status— so we know what's synced, what's drafted, and what diverged. - Every push command is documented — the skill maps each section to the
ascsubcommand that pushes it, or flags it asmanual_onlywhen no API exists.
This skill never stores app-specific copy inline; it points at the files. Copy lives in ./metadata/, and any research should live in project-local references.
When to use
Invoke on any of these triggers:
- Creating or editing App Store copy, subtitle, keywords, description, promo text, or What's New
- Preparing a new version for submission (
asc release,asc submit) - Auditing whether ASC is in sync with the repo
- Adding a locale or an IAP/subscription
- Changing pricing, category, age rating, review info, or privacy declarations
- Before
asc metadata push— verify the YAML passes schema checks - After
asc metadata pull— reconcile drift into the YAML
Directory layout
metadata/
├── app.yaml # app identity (name, bundle, sku, primary locale, platforms, content rights)
├── version.yaml # current version info (versionString, copyright, releaseType, releaseDate)
├── categories.yaml # primary + secondary category
├── age-rating.yaml # age rating declarations
├── content-rights.yaml # third-party content declaration
├── encryption.yaml # export compliance (ITSAppUsesNonExemptEncryption + exemptions)
├── privacy.yaml # App Privacy (data categories × purposes × linkage × tracking)
├── pricing.yaml # price point + territory availability
├── review-info.yaml # review contact + demo account + reviewer notes
├── testflight.yaml # beta license, feedback email, beta description, review contact
├── screenshots.yaml # per-device-class manifests, paths to PNG/MP4 assets
├── locales/
│ ├── en-US.yaml # per-locale copy: subtitle, description, keywords, promo, whatsNew, URLs
│ └── <other-locales>.yaml
├── iap/
│ └── <product-id>.yaml # one file per IAP: type, price, review screenshot, localizations
├── subscriptions/
│ └── <group-ref-name>.yaml # one file per subscription group, with its subscriptions nested
├── status.yaml # auto-generated rollup (do not edit by hand)
└── README.md # link back to this skill
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 116 lines · 165 tokens per session scan A 3d72ce031952
asc-metadata-yaml is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 165 tokens to every session and 1,594 once invoked, about $0.0008 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 skills, from other repositories
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.