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 commands/ofcskn/mobile-automation-plugin/msd-asogit clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWrote 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/ofcskn/mobile-automation-plugin/msd-aso)<a href="https://agentmods.dev/commands/ofcskn/mobile-automation-plugin/msd-aso"><img src="https://agentmods.dev/badge/commands/ofcskn/mobile-automation-plugin/msd-aso.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.00013 | $0.00204 |
| Opus 5 | $0.00006 | $0.00102 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
msd-aso 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 5d 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 ASO optimization for the specified app.
Ask: app ID, target locale(s), top 3 competitors.
Steps:
- Load
skills/optimizing-aso-seo - Load
lenses/aso-optimizer.lens.md - Gather: app description draft (read from README or ask user), competitor names
- Run the ASO optimizer lens for the primary locale first, then each additional locale
- After user approves output, write to
.msd/metadata/{appId}/ios/{locale}/and.msd/metadata/{appId}/android/{locale}/ - Validate:
node skills/managing-store-metadata/scripts/validate-metadata.js {appId} - Cross-reference top keywords with
lenses/screenshot-designer.lens.mdfor OCR alignment
Run the lens once per locale — keyword research differs by language and market.
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.
- 5d ago First seen · 19 lines · 13 tokens per session scan A 6777dc371b0d
msd-aso is a command published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 204 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
translate
Translate content into 15 languages while preserving brand voice, citations, and SEO optimization.
add-string
Add a user-facing string/plural to all 16 locales (Android + iOS).
moodle-string-check
You will find untranslated user-facing strings in a Moodle plugin.
language
Toggle the HUD label language between English and 中文 (edits /.claude/plugins/balance-hud/config.json).
translate
Translate a legal document from any language to English.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.