AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Netcat Async

skill-02loveslollipop-opencrow-netcat-async · by 02loveslollipop

Maintain bidirectional netcat-style TCP communications with persistent asynchronous input/output. Use when an agent must keep a connection open across multiple commands, send messages while receiving background output, inspect connection logs, or safely start/stop reusable sessions for protocol testing, CTF services, debugging sockets, or interactive line-based services.

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-02loveslollipop-opencrow-netcat-async

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-02loveslollipop-opencrow-netcat-async)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Netcat Async? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

OpenCROW I/O - Netcat Async

Runtime preflight

Probe required commands with command -v and Python modules with importlib.util.find_spec before use. Prefer a PATH-resolved OpenCROW MCP helper or the ctf/sage environment when available, then the managed helper or system Python. If a capability is missing, stop that path safely and report the exact missing command or module.

Prefer the opencrow-netcat-mcp server for session lifecycle, reads, and writes. Fall back to scripts/ncx only when you need to inspect or debug the backend directly.

MCP First

  • Use toolbox_info, toolbox_verify, and toolbox_capabilities first.
  • Use the generic session tools:
  • session_start
  • session_listen
  • session_send
  • session_read
  • session_status
  • session_stop
  • Keep one named session per target flow so the MCP server can report stable artifacts under /tmp/opencrow-nc-async//.

Use scripts/ncx to manage long-lived TCP sessions instead of one-shot nc invocations when you are operating outside MCP.

Workflow

  1. Start a named outbound session, or listen for one inbound connection.
  2. Send one or more payloads while the daemon keeps receiving output asynchronously.
  3. Read logs (tail for recent data, follow for streaming).
  4. Stop the session when done.

Commands

# Start session
scripts/ncx start --name demo --host 127.0.0.1 --port 9001

# Listen on loopback for one inbound connection (port 0 selects a free port)
scripts/ncx listen --name inbound --port 0

# Send text (append newline for line-oriented protocols)
scripts/ncx send --name demo --data 'ping' --newline

# Send exact bytes using hex or strict base64
scripts/ncx send --name demo --hex '00 03 ff'

# Read latest output
scripts/ncx read --name demo --tail 40

# Follow output live
scripts/ncx read --name demo --follow

# Check metadata and process state
scripts/ncx status --name demo

# Stop session
scripts/ncx stop --name demo

Operational Rules

  • Use one session per target/service flow (--name scoped per host+port interaction).
  • Prefer --newline for interactive text protocols.
  • Non-loopback listeners require --allow-remote; restrict known peers with --expected-peer.
  • Read with --tail before --follow to avoid missing context.
  • Stop sessions explicitly to avoid stale daemons.
  • If status reports running: false, inspect daemon.log and restart.

Files and State

Session state lives at /tmp/opencrow-nc-async//:

  • io.log: timestamped TX/RX events
  • rx.raw: raw received bytes
  • daemon.log: daemon stdout/stderr
  • meta.json: session metadata
  • pid: daemon PID

References

  • For usage patterns and recovery steps, read references/patterns.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills