competition-web-runtime

Name: competition-web-runtime
Availability: InStock
Author: xjtu-wang

Map live web requests and routing decisions in sandboxed environments.

4|Updated Apr 9, 2026

Search Tags:#routing #traceability #sandbox #analyze #security-analysis #web-runtime

Ready to run

npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-web-runtime

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: competition-web-runtime
Source: https://github.com/xjtu-wang/DigAgent/tree/main/.agents/skills/competition-web-runtime
Command: npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-web-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps security analysts diagnose and understand web behavior inside a sandbox by mapping live requests, routing decisions, and authentication state to reveal how a site operates under controlled conditions.

Core Features & Use Cases

Map active runtime by identifying hosts, paths, proxies, containers, and workers, and by inspecting browser storage and service workers.
Capture exact request order, headers, cookies, and responses to compare successful and failing flows and verify gating logic.
Use cases include debugging routing and session flows, verifying sandbox assumptions, and tracing upstream and downstream interactions in a web app.

Quick Start

After the sandbox is established, activate the competition-web-runtime to begin inspecting live HTTP flows and routing behavior.

Frequently Asked Questions about competition-web-runtime

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

FAQPage Schema

How do I trace live web requests and routing behavior in a sandboxed environment?▼

Map live web requests by capturing exact order, headers, cookies, and responses to compare successful and failing flows. This documents state transitions and reveals gating logic across entry points.

What is the best way to debug routing and session flows behind proxy architectures?▼

Debug routing and session flows by inspecting browser storage, service workers, and proxy paths. This traces upstream and downstream interactions while verifying sandbox assumptions in worker-based architectures.

Can I use this to inspect web apps operating behind authentication walls and worker-based architectures?▼

Yes, inspecting web apps behind authentication walls and worker-based architectures is supported. The tool maps request order and identifies gating logic by documenting exact requests, responses, and state transitions.

How do I document exact requests, responses, and state transitions for security analysis?▼

Document exact requests, responses, and state transitions by activating the runtime inspection after the sandbox is established. This satisfies requirements for precise evidence collection and route tracing.

Why does my sandboxed web behavior fail behind proxy routing and how can I diagnose it?▼

Sandboxed web behavior fails due to incorrect routing or gating logic. Diagnose it by comparing successful and failing flows through exact request capture, verifying sandbox assumptions against documented state transitions.