More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    iOS Info.plist Check

    1

    NSAllowsArbitraryLoads gets questions from App Review, a secret in Info.plist is readable by anyone who unzips the .ipa, and a vague camera permission text gets the build rejected.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    iOS Info.plist Check

    iOS Info.plist Check

    Example session with this skill installed

    Check this project with ios-info-plist-check.

    • Read your context and instructions
    • Compiled the ios info plist

    $ python3 scripts/check_plist.py examples/risky
    BLOCK App/Config.plist:7 I02 SECRET_IN_APP_CONFIG
    <key>API_SECRET</key>
    Why: An API secret, client secret, token or password is written in a plist or .xcconfig that is committed (or shipped in the app bundle). Anyone can unzip an .ipa and read plists, so the secret is public.
    Safer: Keep secrets on your server and have the app call it. For build-time values, use a git-ignored .xcconfig or CI secrets, and rotate any secret that was committed.

    BLOCK App/Info.plist:9 I01 ATS_TURNED_OFF
    BLOCK Config/Release.xcconfig:2 I02 SECRET_IN_APP_CONFIG
    BLOCK keys/AuthKey_EXAMPLE00.p8 I03 PRIVATE_KEY_FILE_IN_PROJECT
    REVIEW App/App.entitlements:5 I15 DEBUG_ENTITLEMENT
    REVIEW App/Info.plist:15 I11 PLAIN_HTTP_EXCEPTION
    REVIEW App/Info.plist:17 I13 WEAK_TLS_EXCEPTION
    REVIEW App/Info.plist:22 I14 WEAK_PERMISSION_TEXT
    REVIEW App/Info.plist:24 I16 FILE_SHARING_ON
    REVIEW ShareExtension/Info.plist:7 I12 ARBITRARY_LOADS_FOR_WEB_OR_MEDIA

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 6 files, 6 with iOS app config content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    NSAllowsArbitraryLoads gets questions from App Review, a secret in Info.plist is readable by anyone who unzips the .ipa, and a vague camera permission text gets the build rejected. This skill finds those and six other Apple app config problems before you submit, and tells you how to fix each one.

    Your agent runs a scanner on your Xcode project: .plist files (XML and binary, read with Python's own plist reader), .xcconfig build settings and .entitlements files, and it notices .p8 and .p12 key files. It follows ATS settings into each exception domain, treats localhost and .local exceptions as development-only, knows that GoogleService-Info.plist keys, client IDs, Facebook client tokens and Mapbox public tokens are meant to be in the app, and reads .gitignore so ignored files are not reported. It never runs Xcode. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • I01: NSAllowsArbitraryLoads set to true (App Transport Security off)
    • I02: an API secret, client secret, token or password in a plist or committed .xcconfig
    • I03: an AuthKey .p8 or a .p12 file in the project that git does not ignore

    REVIEW

    • I11: plain HTTP allowed for a real domain
    • I12: arbitrary loads allowed in web views or media
    • I13: TLS 1.0 or 1.1, or no forward secrecy, for an exception domain
    • I14: empty, very short or placeholder permission texts (NS...UsageDescription)
    • I15: get-task-allow in an entitlements file
    • I16: UIFileSharingEnabled on

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example app config, and the real report the scanner produces on the risky one

    Limits It reads files as written: settings added at build time, Swift code, the signed app bundle and App Store Connect settings are not checked. NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    Static check of plist, .xcconfig and .entitlements files. Build-time settings and Swift code are not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example config includes clearly fake, inert secrets (not-a-real-...) and an inert sample key file for the scanner to find. Nothing is run.

    Listed7 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads your plist, .xcconfig and .entitlements files as text with Python. It runs on macOS, Linux and Windows and never runs Xcode.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    New in Mobile Development