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 skills add ccoalm/ccl-skills --skill app-cross-platform-devgit clone --depth 1 https://github.com/ccoalm/ccl-skillsWrote 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/ccoalm/ccl-skills/app-cross-platform-dev)<a href="https://agentmods.dev/skills/ccoalm/ccl-skills/app-cross-platform-dev"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/app-cross-platform-dev.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.00171 | $0.09659 |
| Opus 5 | $0.00086 | $0.04829 |
| Sonnet 5 | $0.00034 | $0.01932 |
| Haiku 4.5 | $0.00017 | $0.00966 |
Grade A, and why
app-cross-platform-dev 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 today.
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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Cross-Platform Dev
Use this skill for mobile app and cross-platform client engineering. It covers Flutter, React Native, native Android, and native iOS. It does not own mini-programs, React web, backend service design, product requirements, or visual design rules. After code/test edits, self-check and invoke code-review automatically before completion.
Routing
- Use
product-rd-workflowfirst when the work spans product intent, architecture, design, implementation, testing, and release. - Use
product-ui-ux-designbefore or alongside coding for user-facing surfaces, interaction model, visual hierarchy, density, motion, empty/error states, and accessibility acceptance. - Use
miniapp-product-devfor WeChat/Alipay/Douyin/Baidu mini-program pages, host-platform APIs, developer tools, real-device preview, review submission, and miniapp release. - Use
web-react-devfor React web and browser-specific client work. - Use Go or Python backend skills for server contracts, persistence, queues, auth services, and API ownership.
- Use
testing-strategyto choose the test layer; return here for Flutter, React Native, Android, or iOS implementation details. - Use
test-artifact-managementfor structured Feishu Bitable cases derived from Feishu requirements or code before implementation. - Use
defect-diagnosisfirst for bugs, failed tests, flaky behavior, crashes, rendering regressions, build failures, or store/release symptoms. - For money, quota, permission, tenant/user data, high-impact AI, repeated submit, async finality, or support-traceable incidents, apply
product-rd-workflowhigh-risk resilience gates before treating the app flow as complete.
Core Workflow
Before editing app code, native project files, platform configs, styles, assets, or tests, complete enough analysis and planning for the change to be reviewable. Scale the plan to risk: a simple low-risk single-screen change can use a short inline plan; multi-platform, API-visible, native-capability, release/store, bug-fix, branch/MR, unclear-risk, or high-risk work needs explicit task split, target-device matrix, acceptance checks, verification commands, rollback or stop conditions, and named handoffs to testing, backend, release, or diagnosis skills before edits. Runtime-visible work additionally consumes the canonical UI/UX delivery contract's Design brief and Test selection Phase 0 before the first implementation edit.
What ships with it
8 files 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.
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.
- today Changed 3f34d61f2b15
- 7d ago First seen · 191 lines · 171 tokens per session scan A 072a5d9562e4
app-cross-platform-dev is a skill published in the GitHub repository ccoalm/ccl-skills (6 stars, last pushed today), licensed Apache-2.0. It adds 171 tokens to every session and 9,659 once invoked, about $0.0009 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
wire-sdk
An SDK integration guide for 앱인토스, a platform for building apps inside Toss. It covers permissions, persistent storage, sharing links, screen controls, safe-area spacing, and secure WebSocket connections.
make-store-assets
A workflow for creating app-store graphics such as a logo, thumbnail, and in-app-purchase icon according to required sizes and available brand evidence. It uses the app specification, brand color, existing supplied assets, and source records to guide the work.
run-preflight
A release pre-check workflow that builds the mini-app, runs automated checks, explains errors, and lists review items that require a person to test the app on a real device. A preflight check is a final inspection before submission.
bitcoin-infrastructure-bluewallet
BlueWallet: mobile Bitcoin + Lightning wallet (iOS/Android). LND on-device + LndHub backend variants. Multi-wallet support. USE WHEN: mobile wallet integrations, evaluating BlueWallet vs Phoenix / Mutiny.
bitcoin-infrastructure-electrum-wallet
Electrum Wallet: classic Python desktop wallet. Lightweight, runs on most platforms, plugin ecosystem, hardware wallet support. USE WHEN: evaluating mature Bitcoin wallet, integrating Electrum protocol clients.
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.