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/smicolon/ai-kit/store-publishingnpx skills add smicolon/ai-kit --skill store-publishinggit clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/smicolon/ai-kit/store-publishing)<a href="https://agentmods.dev/skills/smicolon/ai-kit/store-publishing"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/store-publishing.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.00044 | $0.00932 |
| Opus 5 | $0.00022 | $0.00466 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
store-publishing 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Store Publishing Guide
Requirements and best practices for App Store and Google Play publishing.
App Store Connect (iOS)
Required Metadata
- App name (30 characters max)
- Subtitle (30 characters max)
- Description (4000 characters max)
- Keywords (100 characters, comma-separated)
- Support URL
- Marketing URL (optional)
- Privacy Policy URL (required)
Screenshots Required
| Device | Size | Required |
|---|---|---|
| iPhone 6.7" | 1290 x 2796 | Yes |
| iPhone 6.5" | 1284 x 2778 | Yes |
| iPhone 5.5" | 1242 x 2208 | Optional |
| iPad Pro 12.9" | 2048 x 2732 | If iPad supported |
App Review Guidelines
- No placeholder content
- Complete functionality
- Accurate screenshots
- Clear privacy policy
- No hidden features
- Proper age rating
Common Rejection Reasons
- Incomplete information
- Bugs or crashes
- Placeholder content
- Misleading screenshots
- Privacy policy issues
- Guideline 4.2 (minimum functionality)
Google Play Console (Android)
Required Metadata
- App name (50 characters max)
- Short description (80 characters max)
- Full description (4000 characters max)
- Application type
- Category
- Content rating
- Privacy policy URL
Graphics Required
| Asset | Size | Format |
|---|---|---|
| App icon | 512 x 512 | PNG (32-bit) |
| Feature graphic | 1024 x 500 | PNG/JPEG |
| Phone screenshots | 16:9 or 9:16 | PNG/JPEG |
| Tablet screenshots | 16:9 or 9:16 | If tablet supported |
Release Tracks
| Track | Purpose | Review |
|---|---|---|
| Internal | Team testing | No review |
| Closed | Limited testers | No review |
| Open | Public beta | Light review |
| Production | Public release | Full review |
Data Safety Declaration
Required information about:
- Data collection practices
- Data sharing
- Security practices
- Data deletion options
Pre-Submission Checklist
iOS
- App icon (1024x1024)
- Screenshots for required devices
- Privacy policy URL accessible
- App description complete
- Keywords optimized
- Age rating set
- In-app purchases configured (if any)
- Export compliance answered
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 · 164 lines · 44 tokens per session scan A abc497fba495
store-publishing is a skill published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 932 once invoked, about $0.0002 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
play-policy-insights
Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
app-store-review
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance…