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 kensaurus/cursor-kenji --skill mobile-capacitor-platformgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/mobile-capacitor-platform)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/mobile-capacitor-platform"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/mobile-capacitor-platform.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.00079 | $0.01682 |
| Opus 5 | $0.00039 | $0.00841 |
| Sonnet 5 | $0.00016 | $0.00336 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
mobile-capacitor-platform 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 4d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capacitor Platform & Pipeline
Degree of freedom: MIXED. Which area to tackle [HIGH freedom]; Capacitor
major matching, cap sync, secrets, and store preflight
[LOW freedom — run exactly].
The native-runtime and shipping layer for Capacitor apps.
enhance-capacitor-uihandles cross-surface layout architecture; this skill handles platform features, native builds, store submission, and migrations.Distilled from cap-go/capgo-skills (48 skills, MIT). For deep per-task playbooks, install the full pack:
npx skills add Cap-go/capgo-skillsorclaude plugin marketplace add Cap-go/capgo-skills.
How to reason
- Version —
@capacitor/coremajor; plugin majors must match - Choose — plugin, deep link, push, offline, OTA, CI, or store
- Wire — entitlements, config, and native files for that capability
- Prove — both platforms or CI iOS; secrets never in the JS bundle
Worked example
Version: Capacitor 8 in
package.json;@capacitor/push-notificationsis still v5. Choose: push — FCM + APNs, not an OTA problem. Wire: bump plugin to v8,npx cap sync, APNs entitlement,google-services.json. Prove: emulator tap opens the deep-linked screen; no keystore in git.
Self-critique before reporting
- Majors match — every plugin major equals the Capacitor major
- Native config present — entitlements / usage strings / plist-or-json for the capability
- Secrets out of band — CI/Keychain only; never committed or bundled
- Right owner — form-factor layout →
enhance-capacitor-ui; listing ASO →plan-aso; native-security plan-only →plan-capacitor-hardening
Version discipline (do this first) [LOW freedom — run exactly]
- Read
package.json: the Capacitor major (@capacitor/core) drives everything. Match plugin majors to it (Capacitor 8 → plugin v8). - Check
capacitor.config.tsforappId,webDir,server.url(live-reload vs bundled), and plugin config. - Confirm the target platforms present (
ios/,android/) before suggesting platform-specific steps.
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.
- 4d ago First seen · 101 lines · 0 tokens per session scan A aa9f34009f51
mobile-capacitor-platform is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 10d ago), licensed MIT. It adds 79 tokens to every session and 1,682 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-database
Use when syncing real-time data, structuring JSON trees, reading/writing, creating listeners, enabling offline persistence, managing presence, sharding, or writing security rules.
generate-images-with-firebase-ai
Use when generating or editing images from Flutter/Dart with Firebase AI Logic and a Gemini image model (Nano Banana), making the first call work, choosing Gemini Developer API vs Vertex AI, hitting quota, billing or App Check failures, getting empty or image-only responses, sending a user photo as input, controlling…
firebase-app-check
Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.