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/cbrock84/headcount/app-store-optimizationnpx skills add cbrock84/headcount --skill app-store-optimizationgit clone --depth 1 https://github.com/cbrock84/headcountWhat 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.00064 | $0.00488 |
| Opus 5 | $0.00032 | $0.00244 |
| Sonnet 5 | $0.00013 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
app-store-optimization 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App store optimization
Two levers, and they are separate problems: being found, and being installed once found. Diagnose which is failing before changing anything.
Being found
The stores index different fields, so the same metadata does not work on both.
- App name / title — the single heaviest field. Brand plus the primary descriptive term. Do not spend it on brand alone.
- Subtitle and keyword field — no repetition across fields; duplicated terms are wasted characters, not reinforcement.
- Long description — indexed on one store, effectively not on the other. Write it for the store that indexes it and for humans on the store that does not.
- Category — pick where you can rank, not where you technically belong.
Target terms with real intent. Ranking first for a term nobody searches is a vanity result.
Being installed
Most visitors decide from the first screenshot and the rating, without scrolling or reading.
- Screenshots — the first two carry the decision. Lead with the outcome or the core screen, with a caption stating the benefit. Never lead with an onboarding or login screen.
- Icon — recognizable at actual size, distinct from category conventions. Test at real scale on a device.
- Rating — the strongest single conversion factor. Prompt for review after a success moment, never on launch or mid-task.
- Video — only if it demonstrates something a screenshot cannot. A weak one costs installs.
Reviews
Respond to negative reviews specifically and without defensiveness, naming the fix and its version where there is one. Prospects read the responses as much as the complaints, and a pattern of real answers converts.
Watch review text for recurring themes — it is the cheapest continuous product research available.
Testing
Change one element at a time and let it run a full weekly cycle; app traffic is strongly day-of-week seasonal. Attributing a lift to the wrong change is worse than not testing.
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.
- 3d ago First seen · 49 lines · 64 tokens per session scan A 6d504463d270
app-store-optimization is a skill published in the GitHub repository cbrock84/headcount (578 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 488 once invoked, about $0.0003 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-30.
Other skills, from other repositories
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
designmatch
Use when matching a React Native screen to a Claude Design HTML canonical at ≥95% visual parity on real Android/iOS hardware — closes the loop with a VQA stub mode, Playwright canonical renderer at 1080×2444, and a dual-metric pixelmatch + SSIM diff harness producing composite triptychs.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
moodle-mobile-app
Use when integrating a Moodle plugin with the Moodle Mobile app — db/mobile.php remote templates, Ionic/Angular components delivered server-side, mobile.php view types, addons, push notifications, and offline support.
uikit-expert
Write, review, or improve UIKit code following best practices for view controller lifecycle, Auto Layout, collection views, navigation, animation, memory management, and modern iOS 18–26 APIs. Use when building new UIKit features, refactoring existing views or view controllers, reviewing code quality, adopting modern…