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 fatihkan/badi --skill mobilegit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/mobile)<a href="https://agentmods.dev/skills/fatihkan/badi/mobile"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/mobile.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.00084 | $0.01241 |
| Opus 5 | $0.00042 | $0.00620 |
| Sonnet 5 | $0.00017 | $0.00248 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
mobile 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Development Skills
This file contains all the skills across mobile app design, development, testing, deployment, and optimization.
Built-in Sub-skills
app-store-screenshots
Auto-generates App Store and Google Play promotional screenshots (Next.js + html-to-image). PNG export at all mandatory Apple/Google resolutions. Triggers: "app store screenshot", "play store screenshot", "marketing asset". Detail: .claude/skills/mobile/app-store-screenshots/SKILL.md
mobile-architecture-design
Picks and applies a scalable, maintainable architectural approach for the mobile app.
cross-platform-strategy
Sets the shared-codebase development strategy for iOS and Android.
react-native-development
Builds best practices and architecture for mobile development with React Native.
flutter-development
Builds mobile development architecture and practices with the Flutter framework.
ios-native-development
Builds the iOS native development guide with Swift and SwiftUI.
android-native-development
Builds the Android native development guide with Kotlin and Jetpack Compose.
mobile-ui-design
Builds UI design principles and a component system for mobile apps.
mobile-navigation
Designs user navigation and screen transitions in the mobile app.
mobile-state-management
Optimizes data flow by designing the mobile state-management strategy.
mobile-performance-optimization
Applies improvement strategies by analyzing the mobile app's performance.
mobile-storage-strategy
Sets the local data-storage approach and strategy in the mobile app.
mobile-networking
Designs and optimizes the mobile app's network communication layer.
mobile-push-notifications
Builds the push-notification infrastructure and notification strategy.
mobile-security-implementation
Applies technical controls and best practices securing the mobile app.
mobile-authentication
Designs user authentication flows in the mobile app.
What ships with it
2 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 First seen · 270 lines · 0 tokens per session scan A 2737aad7c527
mobile is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,241 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-06.
Other skills, from other repositories
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
landing-page-generator
Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.