request-import

Parse HAR exports and raw HTTP requests into structured endpoint and authentication inventories.

3|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill request-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-import
Source: https://github.com/EntroVyx/hermes-agent-offsec/tree/main/skills/offsec/meta/request-import
Command: npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill request-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of manually parsing large volumes of captured HTTP traffic, transforming raw HAR or Burp/Caido files into structured, actionable offensive security intelligence.

Core Features & Use Cases

  • Automated Traffic Mapping: Automatically extracts endpoints, parameters, cookies, and authentication artifacts from captured requests.
  • Offensive Classification: Categorizes traffic into high-risk clusters like GraphQL, auth recovery, or business logic workflows.
  • Use Case: After performing a manual recon session, import your HAR file to instantly generate a dossier of high-risk parameters and suggested attack paths for deep-hunting.

Quick Start

Use the request-import skill to parse the captured traffic file located at path-to-file.har and generate an offensive request map.

Frequently Asked Questions about request-import

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

FAQPage Schema
How do I parse HAR files to map endpoints and parameters for pentest recon?

To parse HAR files for pentest recon, you can use a script to automatically extract and map endpoints, parameters, and cookies into structured offensive intelligence, generating an actionable markdown report of your attack surface.

What is the best way to extract authentication artifacts from captured HTTP traffic?

Extracting authentication artifacts from captured HTTP traffic is best handled by using an automated parser to classify raw request files and HAR exports, identifying high-risk clusters like auth recovery workflows to suggest targeted manual hunting modes.

Can I use raw HTTP request files to identify high-risk attack surfaces without manual review?

Yes, you can use raw HTTP request files to identify high-risk attack surfaces without manual review by importing them into a traffic mapping script that categorizes traffic into offensive clusters like GraphQL and business logic workflows.

Does this traffic parsing approach work with Burp Suite and Caido exports?

Yes, this traffic parsing approach works with Burp Suite and Caido exports, as it is designed to process HAR exports and raw HTTP request files captured from proxy tools, transforming them into structured offensive security intelligence.

Do I need Python 3 to process and classify HTTP traffic data from HAR exports?

Yes, you need Python 3 with standard library support to process and classify HTTP traffic data from HAR exports, as the parsing script relies on this environment to build a structured inventory of endpoints and parameters.

When should I not use automated traffic mapping for offensive security workflows?

You should not use automated traffic mapping for offensive security workflows when dealing with unstructured or non-HTTP protocol traffic, as the parser specifically requires standard HAR exports or raw HTTP request files to classify endpoints and suggest attack paths.