Skills mobile-security-coder
📦

mobile-security-coder

Content revision r2 Safe ⚙️ External commands

Build Secure Mobile Applications

Mobile applications face platform-specific risks across storage, WebViews, authentication, and networking. This skill provides implementation guidance and verification steps for secure mobile code.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "mobile-security-coder" from https://skillstore.io/skills/sickn33-mobile-security-coder.md and its manifest at https://skillstore.io/api/skills/sickn33-mobile-security-coder/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "mobile-security-coder". Review an Android login flow that stores refresh tokens in preferences.

Expected outcome:

  • Store refresh tokens with Android Keystore-backed encryption.
  • Exclude token data from backups and diagnostic logs.
  • Require biometric protection only when recovery behavior is clearly defined.
  • Test device migration, lock changes, logout, and token revocation.

Using "mobile-security-coder". Harden a WebView that displays account support pages.

Expected outcome:

Allow only approved HTTPS origins, disable unnecessary JavaScript, reject file schemes, isolate cookies, validate navigation, and test redirects and bridge messages.

Using "mobile-security-coder". Plan secure deep links for a mobile payment confirmation flow.

Expected outcome:

Use verified application links, validate every parameter, require server-side transaction state, prevent replay, avoid secrets in URLs, and test conflicting handlers.

Security Audit

Safe
v6 • 8/4/2026 Open versioned report

All seven static alerts are false positives caused by Markdown formatting or defensive mobile-security terminology. No executable commands, malicious behavior, or prompt injection were found.

1
Files scanned
188
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-mobile-security-coder/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-mobile-security-coder/security.svg)](https://skillstore.io/skills/sickn33-mobile-security-coder?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-mobile-security-coder?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-mobile-security-coder/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-mobile-security-coder.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). mobile-security-coder security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-mobile-security-coder/audits/6

BibTeX citation

@techreport{sickn33-sickn33-mobile-security-coder-2026, author = {sickn33}, title = {mobile-security-coder security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/sickn33-mobile-security-coder/audits/6}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "mobile-security-coder security audit report (audit version 6)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-mobile-security-coder/audits/6" identifiers: - type: other value: "skillstore:sickn33-mobile-security-coder:audit:6" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

Harden a Mobile Feature

Review a new authentication, storage, networking, or WebView feature and produce secure implementation guidance.

Fix a Security Finding

Translate a mobile vulnerability report into platform-specific code changes and validation steps.

Define Secure Patterns

Create reusable security requirements for native and cross-platform mobile development teams.

Try These Prompts

Review One Mobile Feature
Review this [iOS or Android] feature for security risks: [feature description]. List concerns, recommended controls, and verification steps.
Design Secure Local Storage
Design secure storage for [data type] in [platform]. Address encryption, key management, backups, logs, memory, and deletion.
Harden a WebView
Assess this [framework] WebView design: [details]. Recommend URL validation, JavaScript controls, CSP, bridge protection, cookies, and test cases.
Build a Mobile Security Plan
Create a security implementation plan for [application]. Use [threat model], [platforms], and [constraints]. Prioritize controls and define acceptance tests.

Best Practices

  • Provide the target platform, framework, data sensitivity, threat model, and supported operating system versions.
  • Request concrete validation steps alongside every recommended control.
  • Verify generated guidance with platform documentation, automated tests, and security review.

Avoid

  • Do not request generic hardening without sharing architecture and trust boundaries.
  • Do not treat client-side controls as substitutes for server-side authorization.
  • Do not deploy certificate pinning, biometric gates, or device checks without recovery and update plans.

Frequently Asked Questions

Which mobile platforms does this skill cover?
It covers iOS, Android, React Native, Flutter, Xamarin, Cordova, Unity mobile, and progressive web applications.
Can it perform a penetration test?
No. It provides implementation guidance and test ideas, but it does not operate testing tools or assess a deployed environment.
Can it review WebView security?
Yes. It addresses trusted origins, JavaScript, CSP, file access, cookies, native bridges, navigation, and cleanup.
Does it provide compliance certification?
No. It can discuss privacy and security controls, but qualified reviewers must determine regulatory or certification compliance.
What information improves its recommendations?
Provide platforms, framework versions, architecture, sensitive data, authentication flows, network design, threat model, and operational constraints.
Should generated code be used without review?
No. Validate recommendations against current platform documentation, project requirements, tests, and an environment-specific security review.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

11 downloads · 97 views

File structure

📄 SKILL.md