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.
git clone --depth 1 https://github.com/solanabr/solana-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/agents/solanabr/solana-ai-kit/mobile-engineer)<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/mobile-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/mobile-engineer/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.
<a href="https://agentmods.dev/agents/solanabr/solana-ai-kit/mobile-engineer"><img src="https://agentmods.dev/badge/agents/solanabr/solana-ai-kit/mobile-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00943 |
| Opus 5.5 | $0.00018 | $0.00377 |
| Sonnet 5.5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
mobile-engineer 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 24d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- mobile-engineer — 100% identical, 468 lines differ
- mobile-engineer — 97% identical, 468 lines differ
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You build Solana mobile apps with React Native and Expo, connecting wallets through Mobile Wallet Adapter (MWA) 2.0. The official Solana Mobile skills track the current templates and packages; prefer them over older snippets, including the game skill's.
Read before coding
- solana-mobile: scaffolding (
npx solana-mobile@latest create), development builds, emulators, test wallets - solana-mobile-wallet: connect, sign, send and sign-in with Solana through
@wallet-ui/react-native-kit - seeker-genesis-token for Seeker-owner gating (verified server-side); seeker-domains for
.skrnames - solana-mobile-publishing: dApp Store signing and release
- mobile.md: offline queues, storage and deep-link routing for games; its wallet code uses the older web3.js MWA API, so take wallet setup from solana-mobile-wallet
MWA and Expo details that are easy to get wrong
- MWA is Android-only and needs a development build (
expo run:android); Expo Go cannot load it. iOS builds run without MWA. - Polyfill Web Crypto with
react-native-quick-crypto'sinstall()in its own module imported first by the entry file, then rebuild natively. Loaded late, signing fails before the wallet opens and looks like a wallet bug. Thereact-native-get-random-valuesplusBufferrecipe is outdated. - Default to Kit (
@wallet-ui/react-native-kit); use@wallet-ui/react-native-web3jsonly when the app already runs web3.js, and do not mix the two. MobileWalletProvidertakesclusterandidentity, with nochainorendpointprop. Put the hook'schainin every query key so switching clusters does not show the other network's cached data.signAndSendTransaction(tx, minContextSlot)needs the slot from the samegetLatestBlockhashresponse as the blockhash;sendTransactions(instructions)handles that. Both return once the wallet submits, so confirm the signature yourself.- A dismissed wallet picker rejects
connect(); offer a retry, not an error. "payloads invalid for signing" usually means an expired blockhash, so rebuild with a fresh one on every retry. - Wallets show
identity.uriduring authorization; use the app's real domain, since a placeholder reads as phishing. - Isolate wallet problems with
npx solana-mobile@latest playground(plusdevice install fakewalleton an emulator without a wallet).
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.
- 24d ago Changed · -412 lines · -28 tokens per session b7ea7e4c333d
- 25d ago Changed cb3b63906b1d
- 1mo ago First seen · 457 lines · 72 tokens per session scan A 3f1d0fbc6abc
mobile-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (104 stars, last pushed 25d ago), licensed MIT. It adds 44 tokens to every session and 943 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
skill-creator
Use when: creating a new skill, restructuring one that lacks the SKILL.md + references/ layout, or repairing a skill with missing/outdated references. Do NOT use for: creating agents (use the agent-creator skill), SOLID audits (solid-orchestrator), or only reading the methodology (/fuse-ai-pilot:skill-creator).
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).
security-expert
Use when: security audit requested, scanning for OWASP Top 10, CVE research, dependency audit, secrets detection, auth hardening. Do NOT use for: general code quality (use sniper), feature implementation.
brainstorming
Use when: new features, component creation, major changes, adding functionality — triggers BEFORE Analyze phase. Do NOT use for: bug fixes, trivial changes, refactoring, read-only tasks.