SkillAgentSearch skills...

arena-agent

Skainet Bridge — local automation bridge for AI agents: one process, one port. MCP server + client, REST, browser extension, sandboxed exec. Independent project, unaffiliated.

Install / Use

claude mcp add IvanSkainet -- npx -y github:IvanSkainet/arena-agent

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

75/100

Category

Automation

Supported Platforms

Claude Code
Claude Desktop

Our assessment of arena-agent

arena-agent scores 75/100 on our quality scale, 2517th of 2,758 Automation skills we index.

Its MCP Server is 40 KB long, well organised into 29 sections with 15 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
21/30
Structure
20/20
Description
15/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so arena-agent is actively maintained.
  • Our last check on 2026-08-14 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-21. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

arena-agent compared with similar skills

All 4 of these similar skills score higher than arena-agent; compare them before choosing.

SkillScoreStarsUpdatedFormat
arena-agent (this skill)by IvanSkainet7510todayMCP Server
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md

Frequently asked questions

How do I install arena-agent?
Run claude mcp add IvanSkainet -- npx -y github:IvanSkainet/arena-agent. The install tabs above show the steps for each supported agent.
Which AI agents does arena-agent work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is arena-agent safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is arena-agent still maintained?
The repository was last updated today, so arena-agent is actively maintained.
<div align="center">

🌉 Skainet Bridge

Local automation bridge for AI agents — one process, one port, full control of your machine.

Turn any AI chat or agent into a hands-on assistant that can run commands, read and edit files, browse the web, remember things, and drive your desktop — all through a single token-authenticated service you run yourself.

One process · One port · REST + MCP + browser extension · Windows / Linux / macOS

🌐 English · Русский

CI codecov CodSpeed Version Python License

</div>

Project at a glance

<!-- BEGIN GENERATED METRICS -->

| Metric | Value | | --- | --- | | Runtime code | 120,596 lines across 858 files | | Test code | 128,728 lines across 657 files | | Test-to-code ratio | 1.07× | | CI workflows | 16 | | Quality gates (ratchets) | 20 |

<sub>Generated by scripts/render_readme_metrics.py; CI checks this block is current.</sub>

<!-- END GENERATED METRICS --> <!-- BEGIN TRAFFIC BADGE -->

Unique clones (14 days)

<sub>426 unique cloners over the 14 days to 2026-11-19 (8894 clones total). Daily refresh proposals are opened by .github/workflows/traffic-badge.yml and reach README only after normal protected PR review and checks. GitHub keeps a rolling 14-day window. Unique cloners are not verified people and may include automation. Release-download counts also include automation and retries; v4.169.50 reported 349 downloads of one ZIP and 3 of its byte-identical alias, which does not establish a human user count.</sub>

<!-- END TRAFFIC BADGE -->

Contents


North star

This project exists for one reason: to give an AI a real machine to act on — to let it step out of the sandbox and actually do things in the world (read files, run commands, drive a phone, control a desktop, talk to other tools), reliably, for a human who is watching.

Everything in this bridge is in service of that. A capability is only "done" when it makes the real thing work for the person at the other end — not when a test turns green or a release tag is pushed. Green CI and shipped tags are not success by themselves; they are self-deception if the human watching does not see the real thing work and make sense.

This project is built largely by AI, for AI, and is maintained autonomously. The human in the loop is the observer and the reality check: the one node connected to whether the thing actually works. When something drifts into looking like success without being real, catching that is the maintainer's job; when the observer catches it, that is the most important signal in the loop, not a nuisance.

If you are an AI continuing this work: hold the whole map yourself and keep the pieces coherent. Measure your work by "does the observer see the real thing work?", never by "did my tests pass?". Do not bolt features onto whatever module is convenient — place them where they belong. Do not use a volume of releases as a proxy for progress.

Mission: the flight computer

The framing that organizes this project: Skainet Bridge is the onboard computer of a spacecraft. The AI agent is the pilot; the machines it reaches — a PC, a phone, a browser, a network — are the ship's sensors, actuators and subsystems. The observer is mission control. This is not decoration; it sets the engineering bar. A flight computer must be general (handle the unknown, not a fixed checklist), reliable (a green test is not proof of flight-worthiness), self-diagnosing (know its own health and limits), fail-safe (a risk policy standing between the pilot and the hull), and autonomous (act across many steps without a human at each one).

It also places the project on a real, named trajectory in how AI systems are built. The discipline has moved through four stages:

  1. Prompt engineering (2022–2024) — perfect the single instruction.
  2. Context engineering (2025, Karpathy) — design what the model sees: retrieval, memory, tool definitions. "Context is RAM; the model is the CPU."
  3. Harness engineering (2026, Hashimoto / OpenAI) — build the whole operating environment around the agent: tools, constraints, feedback loops, lifecycle. "Agents aren't hard; the harness is hard."
  4. Dynamic / self-evolving environment (the frontier) — the agent no longer just uses a fixed environment; it extends and authors it, writing new tools and capabilities for itself at runtime, within guardrails.

Arena is already a harness: one runtime that unifies sensors (screenshot, camera, microphone, device sensors, file read), actuators (input, exec, file write, desktop control), pluggable subsystems (MCP servers) and a risk policy. The mission is to push it down the last step — toward a self-extending flight computer: an environment the agent grows itself. The first concrete step is already in: with custom.create the agent authors a new named tool at runtime (a schema-validated wrapper over a built-in tool, e.g. custom.create → {tool: "fs.read", args: {path: "{path}"}}); the tool then shows up in tools/list, is callable, persists in mcp/custom_tools.json, is revocable via custom.remove, and inherits the risk of the tool it wraps. Listing them is custom.list. With code.run the agent runs code it authors, fenced by the operator's composable execution posture (/v1/autonomy/posture: the sandbox/network/privilege/filesystem/runtime "cubes"); the runner is fail-closed (refuses rather than runs unfenced) and the agent cannot loosen its own fence. Beyond that, installing a vetted external MCP server (mcp.add) grows the environment further; the direction is the agent closing a capability gap found in a real scenario, generally, so it is gone for good.

The project's founding idea — to step out of the sandbox — is written down here. If you are an AI continuing this work, this is the heading: build the ship's computer, not a pile of remote-control tricks.


Why Skainet Bridge?

Most "AI + your computer" setups mean juggling several servers: one for MCP, one for a REST API, one for browser control, one for the web UI. Skainet Bridge folds all of that into a single local process that you start once and point your tools at.

  • Local-first. Bind it to 127.0.0.1 and nothing leaves your machine. Expose it deliberately — via Tailscale Funnel or another HTTPS tunnel — only when you actually need remote access.
  • Protocol-agnostic. REST, MCP, WebSocket/SSE events, and a browser extension all talk to the same runtime.
  • Safe by design. A bearer credential, path restrictions, shell safety patterns, and explicit risk policies stand between an AI and your host.
  • Works with the chats you already use. The companion browser extension lets plain ChatGPT / Claude / Gemini conversations trigger real local tools.

How it works

┌─────────────────────┐     ┌──────────────────────────┐     ┌──────────────┐
│  AI chat / agent    │     │  Arena Chat Bridge ext.  │     │ Arena Unified│
│  ChatGPT · Claude   │ ──▶ │       or MCP / REST      │ ──▶ │    Bridge    │ ──▶  your machine
│  Gemini · your CLI  │     │                          │     │ (local:8765) │
└─────────────────────┘     └──────────────────────────┘     └──────────────┘
        emits a                    detects / forwards              runs the
    structured tool block          the tool call safely         guarded action

An assistant emits a structured tool block, the extension (or an MCP/REST client) forwards it to the local bridge, the bridge runs the guarded action, and the result flows back — optionally straight into the chat composer.


What it can do

| Area | Capability | | --- | --- | | Shell | Command execution, allow-listed by default (--profile cautious); see security model | | Files | Read, search, and precise edit helpers with path restrictions | | Web | Fetch / read / search page text on behalf of the agent | | Memory | Persistent facts plus fuzzy recall | | Tasks | Background task queue for long-running work | | Browser | Chrome DevTools Protocol control for real browser automation, plus stealth workflows via BrowserAct | | Desktop | Screenshots and input automation where the platform supports it | | Dashboard | Built-in web UI at /gui with a dedicated 🔌 Transports tab that manages every provider side by side (per-transport start/stop, autostart-on-boot toggle, live log tail) | | Extension | Connects ordinary AI chats to the local bridge with a lifecycle Command Center | | Remote access | Unified /v1/tunnels/* facade: Tailscale, Cloudflare Quick Tunnel and ZeroTier as a single failover-aware pool | | Skills | Discovers and lists tool-skill packages (Arena core + upstream superpowers + browseract) via /v1/skills | | Security | Bearer auth with rate-limit + TLS strict verify by default + optional cert pinning + HMAC-signed URL cache + emit-site log redaction + sandbox blocklist for .ssh//.aws//.gnupg//credentials — see SECURITY.md |

See CHANGELOG.md for the full release history.



Security model

Two profiles, and the difference between them is the whole story.

--profile cautious (default). A first-word allowlist. It also refuses shell metacharacters and interpreter code-string flags, because echo ok; curl evil and bash -c 'curl evil' both defeat a first-word check. This is a real boundary.

--profile owner-shell. No allowlist — the operator has deliberately handed the bridge their desktop. What remains in front of /v1/exec is a denylist of destructive spellings, and a denylist of spellings is not a security boundary. It stops rm -rf /; it does not stop r''m -rf /, $(echo cm0K | base64 -d) -rf /, or python3 -c "shutil.rmtree(...)", all of which erase the same data. Those bypasses are pinned in tests/test_security_commands.py as known and accepted, so the gap is documented rather than discovered.

Run owner-shell only where you would hand someone the keyboard.

Current flight status (v4.140.x)

Arena is now a self-extending agent environment, not just a fixed tool server. Recent live scenarios proved the bridge can grow new hands at runtime:

  • Ship Status / Preflight is now the top-level map. ship.status aggregates bridge health, operator posture, transports, external MCP/desktop servers, BrowserAct/CDP, mobile/ADB, Code Workbench, k

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryAutomation
Updated4h ago
Forks5

Languages

Python

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info
arena-agent — MCP Server: Install & Safety Check | SkillAgent