solana-mobile-publishing

solana-mobile-publishing is a skill for Claude Code, Codex from solana-mobile/solana-mobile-skills. It costs 76 tokens per session (3,919 once invoked), scanned A, original, Apache-2.0.

A release workflow for building, signing, and publishing Android APK files to the Solana dApp Store, a marketplace for Solana-based apps. It also covers first-time publisher setup and release-build troubleshooting.

In plain words
What is it for?
Use it to create a publisher account, set up an App NFT, build a release APK, sign it, publish it, or investigate why a release build fails when debug works.
Why use it?
It prevents common publishing mistakes, such as uploading an Android app bundle instead of an APK or using a different signing key for an update. It also highlights the permanent wallet and keystore choices involved.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create a publisher account, set up an App NFT, build a release APK, sign it, publish it, or investigate why a release build fails when debug works.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing
Install

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.

Any agent
npx skills add solana-mobile/solana-mobile-skills --skill solana-mobile-publishing
Clone the repo
git clone --depth 1 https://github.com/solana-mobile/solana-mobile-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for solana-mobile-publishing

README.md
[![agentmods](https://agentmods.dev/badge/skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing/github.svg)](https://agentmods.dev/skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing)
Your own site
<a href="https://agentmods.dev/skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing"><img src="https://agentmods.dev/badge/skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing/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.

agentmods 80×15 button for solana-mobile-publishing

Your own site · 80×15
<a href="https://agentmods.dev/skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing"><img src="https://agentmods.dev/badge/skills/solana-mobile/solana-mobile-skills/solana-mobile-publishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,919 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 16 Sept 2026
  • Snyk pass 16 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.03919
Opus 5.5 $0.00030 $0.01568
Sonnet 5.5 $0.00015 $0.00784
Haiku 4.5 $0.00008 $0.00392

Measured 15d ago against content hash 02ca00365159, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-01, from the pricing page.

Security

Grade A, and why

solana-mobile-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 15d 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.

skills/solana-mobile-publishing/SKILL.md · 322 lines

How it starts

The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Publishing to the Solana dApp Store

Shipping to the dApp Store splits into a one-time setup that mints an on-chain App NFT, and a per-release loop of build, sign, publish. The one-time half is where the irreversible decisions live, so get it right before the first release rather than after.

npm install -g @solana-mobile/dapp-store-cli@latest

Node 18 or newer. npx @solana-mobile/dapp-store-cli works too if you would rather not install globally.

Use 1.0.1 or newer. Earlier versions are deprecated and will not work.

Non-negotiable constraints

APK only. An .aab is rejected. Build with assembleRelease, never bundleRelease. This catches out anyone whose muscle memory comes from Google Play, where the bundle is the default.

The keystore and the publisher wallet are both permanent. An update has to be signed with the same key as the release before it, and the App NFT lives in the publisher wallet. Lose either and there is no recovery path and no support ticket that fixes it — the app can only be re-listed from scratch under a new identity. Neither belongs inside the repository: ask where the keystore should live before generating one, and keep it out of the project tree.

If you also ship to Google Play, use a different signing key. One key per store. Sharing one means a compromise or loss takes out both listings at once.

First: work out which situation you are in

Situation Do this
No publisher account yet One-time setup
Publisher exists, shipping a release Build a signed APK, then Publish
Shipping an update to a live app Shipping an update
Release build crashes but debug is fine Read references/signing.md
A publish died partway through Resume a failed publish
App is a wrapped web app, not React Native Web apps

Read the full file on GitHub · 322 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 15d ago First seen · 322 lines · 76 tokens per session scan A 02ca00365159

Subscribe to this mod's changes

solana-mobile-publishing is a skill published in the GitHub repository solana-mobile/solana-mobile-skills (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 76 tokens to every session and 3,919 once invoked, about $0.0003 per session on Opus 5.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-09-16.