mtest

Coordinate phase-driven mobile security testing workflows for Android and iOS.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/n4igme/randscript --skill mtest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mtest
Source: https://github.com/n4igme/randscript/tree/main/llm/skills/mtest
Command: npx skills add https://github.com/n4igme/randscript --skill mtest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

mtest provides a structured framework for performing end-to-end mobile security testing across Android and iOS, coordinating static analysis, bypass attempts, traffic analysis, vuln analysis, and API testing within a repeatable workflow.

Core Features & Use Cases

  • Phase-based routing and governance: Preflight, Static, Bypass, Traffic, Attack Surface, Runtime, Vuln Analysis, API, Exploitation, and Reporting.
  • Cross-platform engagement: Per-platform workflows for Android and iOS with shared phases and per-platform findings.
  • Cross-skill integration: Outputs findings for cross-skill chaining (ptest/atest/ctest) and PoCs for high-severity issues.

Quick Start

Start a new engagement with mtest and immediately run Phase 1 preflight to scaffold the work directory.

Frequently Asked Questions about mtest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured mobile security testing framework for Android and iOS?

A structured mobile security testing framework coordinates phase-driven workflows for Android and iOS, covering static analysis, bypass testing, traffic analysis, vuln analysis, and API testing to enforce repeatable end-to-end engagements.

How do I start a mobile pentest engagement and scaffold the work directory?

To start a mobile pentest engagement, initiate the preflight phase to scaffold the structured phase directory layout, which organizes per-phase outputs, PoC tracking, and findings.jsonl for the entire workflow.

Can I chain mobile pentest findings with API testing and vuln analysis outputs?

Yes, mobile pentest findings support cross-skill chaining, outputting structured data for API testing and vuln analysis while tracking high-severity PoCs to integrate with downstream security tools.

Does this mobile security framework enforce phase gates for static and traffic analysis?

Yes, the mobile security framework enforces phase gates across static analysis, bypass testing, traffic analysis, and attack surface mapping, ensuring structured per-phase outputs before advancing to runtime or exploitation phases.

What is the best way to track proof of concepts during iOS and Android vuln analysis?

The best way to track proof of concepts during iOS and Android vuln analysis is using findings.jsonl within a structured phase directory, which records per-platform findings and high-severity PoC artifacts.

When should I not use a phase-driven workflow for mobile application pentesting?

A phase-driven workflow for mobile application pentesting is not suitable for ad-hoc, single vulnerability checks, as it enforces strict phase gates, per-phase outputs, and structured directory layouts designed for comprehensive engagements.