linxidnju

OpenTag — Security skill for Claude Code

Security community

Open-source, channel-native agent gateway for Slack.

How to install OpenTag

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

What OpenTag does

Open-source, channel-native agent gateway for Slack. Route team threads to Claude Code, Codex, OpenCode, Docker, HTTP agents, and custom CLIs with policy, approvals, memory, audit logs, and artifacts.

Alternatives in Security

  • Promptmap — Security scanner for custom LLM apps 1.2k ★
  • ThinkWatch — Self-hosted AI API and MCP gateway for organizations: SSO and RBAC, per-user identity for MCP tool calls, PII 817 ★
  • Maestro Knowledge — Intent-driven knowledge-store and Run knowledge lifecycle management — audit/prune, stage candidates (with sig 530 ★

README

OpenTag banner

OpenTag

Open-source, channel-native multiplayer AI gateway with shared, auditable team knowledge.

Tag local AI agents into Slack threads, with local execution, visible progress, approvals, audit trails, and pluggable agent runtimes.

English · 简体中文 · User Guide · Security · Contributing

License Node Slack first Status

OpenTag brings AI agents into the place where team work already happens: Slack channels and threads.

Instead of running an agent from one person's terminal and pasting results back into chat, a team can mention `@OpenTag`, discuss the task in the same thread, approve risky actions when needed, and keep the outcome visible to everyone who has access to that channel.


✨ What You Can Do

  • Ask an agent to investigate a bug from a Slack thread.
  • Let teammates add context before or during the agent run.
  • Route work to different agent backends such as Codex, Claude Code, OpenCode, Docker-based agents, HTTP agents, or custom CLIs.
  • Teach OpenTag an explicit team fact, decision, convention, preference, or procedure; corrections are versioned, scoped, sourced, and reused by every configured runtime.
  • Use Channel Profiles / Access Bundles so different projects can have different permissions, memories, default agents, and run limits.
  • Require approvals before write actions