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/geekfujiwara/codeappsdevelopmentstandard/mobile-appsnpx skills add geekfujiwara/CodeAppsDevelopmentStandard --skill mobile-appsgit clone --depth 1 https://github.com/geekfujiwara/CodeAppsDevelopmentStandardWhat 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.00059 | $0.02342 |
| Opus 5 | $0.00030 | $0.01171 |
| Sonnet 5 | $0.00012 | $0.00468 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
mobile-apps 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 2d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Apps Native Mobile Code Apps 開発スキル
Microsoft 公式 microsoft/power-platform-skills/plugins/mobile-apps を upstream として、
Expo + React Native + TypeScript の Native Mobile Code App を作成する。
[!CAUTION] Private Preview であり、本番利用は禁止。 スキル開始時、計画承認時、最終結果でこの制約を明示する。 ユーザーが Preview 利用を明示承認するまで scaffold、環境変更、Wrap 登録、push を開始しない。
Web Code App との境界
「モバイル対応」の依頼では、最初にどちらを求めているか確認する。
| 選択肢 | ランタイム | 選ぶ条件 | スキル |
|---|---|---|---|
| レスポンシブ Web Code App | React + Vite、ブラウザ/Power Apps player | PC とモバイルで同じ Web UI、ネイティブ機能が不要 | code-apps |
| Native Mobile Code App | Expo + React Native、Power Apps Developer app/Wrap | カメラ、バーコード、位置情報等の端末機能が必要 | 本スキル |
Native 経路は Preview 承認に加え、対象 OS、必要な端末機能、オンライン要件、実機テスト端末を確認する。
ワークフロー
Step 0: Preview 利用を確認する
次を説明し、明示承認を得る。
- Private Preview で本番利用できない。
- iOS / Android のローカル native build や App Store / Google Play 配布は v0 の対応範囲外。
- 公式対応は Power Apps Developer app による実機 preview と、
power-apps push後の Wrap 導線まで。 - Preview の破壊的変更に備え、upstream commit と依存セットを固定する。
承認がない場合は code-apps のレスポンシブ Web 案を提示して停止する。
承認後の scaffold は mobile-preview-approval.json を生成する。検証器はこの記録がなく、または
productionAllowed: true のプロジェクトを拒否する。
Step 1: 要件とネイティブ機能を設計する
対象 OS、画面、データ、コネクタ、認証、端末機能、オンライン/オフライン要件を整理する。
端末機能は公式テンプレートの package.json に存在する module だけを候補にする。
- Phase 1: Dataverse/connector、基本画面、camera/location/barcode、実機 preview、push
- Phase 2: PDF、pen/signature、File/Image、sharing、生体認証
- Phase 3: Offline Profile の authoring/assignment/drift check
オフライン runtime store/sync queue は upstream 対応を確認できるまで実装済みと扱わない。
Step 2: 公式テンプレートを生成する
Windows PowerShell 7 で、記録済み upstream commit から生成する。
python .github/skills/mobile-apps/scripts/scaffold_mobile_app.py `
--target ./my-mobile-app `
--preview-approved `
--install
Set-Location ./my-mobile-app
依存は upstream-template.json の互換性セットを使う。
Expo、React Native、Tamagui、native host、Power Apps SDK を個別に latest へ上げない。
What ships with it
11 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.
- references/.env.example 515 B
- references/build-reference.md 3.3 KB
- references/mobile-ui.md 1.4 KB
- references/native-capabilities.md 2.2 KB
- references/offline.md 1.1 KB
- references/troubleshooting.md 2.5 KB
- references/upstream-template.json 764 B
- scripts/check_upstream.py 1.4 KB runs code
- scripts/scaffold_mobile_app.py 5.1 KB runs code
- scripts/test_validate_mobile_project.py 1.2 KB runs code
- scripts/validate_mobile_project.py 6.2 KB runs code
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.
- 2d ago First seen · 190 lines · 59 tokens per session scan A 37bf278e4022
mobile-apps is a skill published in the GitHub repository geekfujiwara/CodeAppsDevelopmentStandard (59 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 2,342 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
tamagui
Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
shadcn-ui-flutter
A comprehensive Flutter UI library inspired by shadcn/ui. Provides high-quality, customizable, and accessible components including Buttons, Cards, Forms, and more. Use this skill when building Flutter UIs, implementing design systems, or needing specific component usage examples.
adapt
Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says "make it responsive" / "fix mobile layout". Invoke when the user asks for adapt…
audit
Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table. Invoke when the user asks for audit on their UI, or mentions 'audit' alongside design / UI / frontend work.
wireframe-prototyping
Creates low-fidelity wireframes and interaction annotations for a feature or screen. Covers user flow identification, ASCII wireframe sketching, interaction annotation, and acceptance criteria. Invoked when the user asks to wireframe a screen, prototype a UI, or sketch a user flow.