inject

Inject ARC Probe into a running Windows x64 process via TCP port 9998.

15|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/vzco/arc-probe --skill inject-vzco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inject
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/inject
Command: npx skills add https://github.com/vzco/arc-probe --skill inject-vzco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inject ARC Probe into a running Windows x64 process to establish a TCP-based inspection session with a live probe server.

Core Features & Use Cases

  • Inject ARC Probe into a running Windows x64 process and verify a successful DLL injection.
  • Validate the target process is running, confirm port availability, and establish a TCP connection to the probe server.
  • Report initial status including target process details, loaded modules, and probe version to guide troubleshooting.

Quick Start

Run the injector with the target process name or PID, then verify the probe is connected with a status query.

Frequently Asked Questions about inject

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

FAQPage Schema
How do I inject a DLL into a running Windows process for inspection?

To inject a DLL into a running Windows x64 process, use an injector binary to target a process name or PID. This establishes a TCP inspection session to verify the injection and connect to a probe server.

What is a TCP-based process inspection session used for?

A TCP process inspection session verifies a successful DLL injection into a running process. It reports initial status including target process details, loaded modules, and probe version to guide troubleshooting.

Do I need administrator privileges to inject a probe into a running process?

Yes, you need an administrator privileged environment to inject a probe into a running process. The injection also requires the specific injector binary, a target process, and port 9998 for the TCP connection.

How do I verify a successful DLL injection into a Windows x64 process?

To verify a successful DLL injection, confirm the target process is running, validate port availability, and establish a TCP connection to the probe server. A status query then reports loaded modules and probe version.

Why does my process injection fail to establish a TCP connection?

Process injection may fail to establish a TCP connection if port 9998 is unavailable or the environment lacks administrator privileges. Validate the target process is running and confirm port availability before injecting.