Bevel-Software

Hexis — AI skill for Claude Code

AI community

Git-backed control plane for AI-agent skills, tools, context, permissions, and identity.

How to install Hexis

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Bevel-Software/Hexis and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Hexis does

Git-backed control plane for AI-agent skills, tools, context, permissions, and identity. Self-hosted and MCP-native.

Alternatives in AI

Phantom — An AI co-worker with its own computer 1.3k ★
Agentrq — AgentRQ: Human-in-loop realtime conversational task manager for AI Agents 1.1k ★
Agenvoy — Self-hosted AI agent harness in a single Go binary — writes, sandbox-tests and repairs its own tools, and lets 474 ★

README

Hexis by Bevel: git-backed skills, tools and context for AI agents

**Git-backed control plane for AI-agent skills, tools, context, permissions and identity. Self-hosted and MCP-native.**

One place where your company's AI plugins, tools and knowledge live: centrally managed, reviewed and access-controlled, and usable from **any AI agent**. The open-source core of the Bevel platform.

Why Hexis?

For teams

One place where engineers and non-technical people alike can browse and load plugins, propose suggestions, and manage access.

For enterprises

Every skill, tool manual and permission is a file in a git repository you own, so the audit trail is the storage layer: who changed what, when, who approved it, and how to undo it. An agent can only do what the person running it can do, resolved per file, and it never holds the credentials it uses. Runs on your infrastructure, behind your own SSO.

Why it's different from MCP gateways:

MCP gateways are uni-directional; users can consume plugins, skills or tools but there is no mechanism here for users to propose changes or share new skills and MCP servers. You can do this via GitHub in the back, but this is n