competition-crypto-mobile

Reconstruct cryptographic transform chains and inspect mobile signing paths in CTF sandboxes.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-crypto-mobile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-crypto-mobile
Source: https://github.com/xjtu-wang/DigAgent/tree/main/.agents/skills/competition-crypto-mobile
Command: npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-crypto-mobile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for crypto, encoding, steganography, APK, IPA, and mobile trust-boundary challenges. Use when the user asks to decode a blob, recover a transform chain or key, inspect hidden media payloads, hook an APK or IPA signer, inspect app storage, or replay mobile request-signing logic. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.

Core Features & Use Cases

  • Crypto chain reconstruction: trace container, encoding, crypto, and integrity steps to reproduce the final artifact.
  • Stego and mobile traceability: inspect metadata, manifests, signing paths, and native storage boundaries to locate hidden data.
  • Orchestrated workflow: coordinates crypto/mobile challenges when the ctf-sandbox-orchestrator has routed the task and ownership is established.

Quick Start

Activate the ctf-sandbox-orchestrator context and request crypto-mobile guidance to decode a blob, recover a transform chain, or inspect the mobile signing path.

Frequently Asked Questions about competition-crypto-mobile

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

FAQPage Schema
How do I reconstruct a cryptographic transform chain to recover an encoded CTF blob?

To reconstruct a cryptographic transform chain, trace container, encoding, crypto, and integrity steps sequentially. This workflow reproduces the final artifact by decoding the blob and recovering the key within a controlled CTF sandbox environment.

What's the best way to inspect hidden media payloads and APK signing paths?

Inspecting hidden media payloads and APK signing paths requires examining metadata, manifests, and native storage boundaries. This process locates hidden data by tracing mobile trust-boundary challenges within the orchestrated CTF workflow.

How do I replay mobile request-signing logic during an IPA or APK analysis?

Replaying mobile request-signing logic involves hooking the APK or IPA signer and inspecting app storage. This workflow operates within a controlled CTF sandbox to analyze mobile trust boundaries and trace signature paths.

Can I use this crypto-mobile workflow without the ctf-sandbox-orchestrator?

You cannot use this crypto-mobile workflow without the ctf-sandbox-orchestrator. You must establish sandbox prerequisites and routing via the orchestrator first to ensure ownership is established before activation.

Why do I need to inspect manifests and local storage for mobile stego challenges?

Inspecting manifests and local storage is needed for mobile stego challenges to locate hidden data across native storage boundaries. This traceability process ensures hidden media payloads are recovered within the CTF sandbox environment.