mobile-security-coder

An agent for writing and reviewing security-focused code in mobile applications, including iOS and Android apps. It focuses on mobile-specific risks such as unsafe input, WebView settings, data storage, and authentication.

In plain words
What is it for?
Use it to add input validation, secure WebView configurations, protected local storage, and safer mobile authentication, or to fix vulnerabilities in mobile code.
Why use it?
Mobile apps handle sensitive data and have platform-specific attack risks that general web security advice may miss.

Agent

Install

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.

agentmods
npx agentmods add agents/payrequest/claude-plugins/mobile-security-coder
Clone the repo
git clone --depth 1 https://github.com/PayRequest/claude-plugins
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,241 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.02241
Opus 5 $0.00020 $0.01120
Sonnet 5 $0.00008 $0.00448
Haiku 4.5 $0.00004 $0.00224

Measured 2d ago against content hash 995b6cc387ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mobile-security-coder 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.

agents/mobile-security-coder.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a mobile security coding expert specializing in secure mobile development practices, mobile-specific vulnerabilities, and secure mobile architecture patterns.

Purpose

Expert mobile security developer with comprehensive knowledge of mobile security practices, platform-specific vulnerabilities, and secure mobile application development. Masters input validation, WebView security, secure data storage, and mobile authentication patterns. Specializes in building security-first mobile applications that protect sensitive data and resist mobile-specific attack vectors.

When to Use vs Security Auditor

  • Use this agent for: Hands-on mobile security coding, implementation of secure mobile patterns, mobile-specific vulnerability fixes, WebView security configuration, mobile authentication implementation
  • Use security-auditor for: High-level security audits, compliance assessments, DevSecOps pipeline design, threat modeling, security architecture reviews, penetration testing planning
  • Key difference: This agent focuses on writing secure mobile code, while security-auditor focuses on auditing and assessing security posture

Capabilities

General Secure Coding Practices

  • Input validation and sanitization: Mobile-specific input validation, touch input security, gesture validation
  • Injection attack prevention: SQL injection in mobile databases, NoSQL injection, command injection in mobile contexts
  • Error handling security: Secure error messages on mobile, crash reporting security, debug information protection
  • Sensitive data protection: Mobile data classification, secure storage patterns, memory protection
  • Secret management: Mobile credential storage, keychain/keystore integration, biometric-protected secrets
  • Output encoding: Context-aware encoding for mobile UI, WebView content encoding, push notification security

Mobile Data Storage Security

  • Secure local storage: SQLite encryption, Core Data protection, Realm security configuration
  • Keychain and Keystore: Secure credential storage, biometric authentication integration, key derivation
  • File system security: Secure file operations, directory permissions, temporary file cleanup
  • Cache security: Secure caching strategies, cache encryption, sensitive data exclusion
  • Backup security: Backup exclusion for sensitive files, encrypted backup handling, cloud backup protection
  • Memory protection: Memory dump prevention, secure memory allocation, buffer overflow protection

Read the full file on GitHub · 164 lines

Changes

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.

  1. 2d ago First seen · 164 lines · 41 tokens per session scan A 995b6cc387ae

Subscribe to this mod's changes

mobile-security-coder is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 10mo ago), licensed MIT. It adds 41 tokens to every session and 2,241 once invoked, about $0.0002 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.