opentag
Reduces context-switching by routing agent requests directly within Slack and GitHub workflows, enabling teams to invoke AI assistance without leaving collab…
Open-source @agent mentions for Slack and GitHub. OpenTag routes tagged requests to Codex, Claude Code, then returns results in thread.
- Route Slack messages to Claude for code review and post results in thread automatically
- Tag GitHub issues with @agent to get AI analysis without leaving the platform
- Automate documentation requests by mentioning Claude in Slack to generate summaries
Reduces context-switching by routing agent requests directly within Slack and GitHub workflows, enabling teams to invoke AI assistance without leaving collaboration tools or managing separate integrations.
Engineering teams using Slack and GitHub who want lightweight agent routing without custom webhook infrastructure or API integration overhead.
https://github.com/amplifthq/opentag
By amplifthq
How to Get It
claude plugins install amplifthq/opentag
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me route Slack messages to Claude for code review and post results in thread automatically
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Hacker News
- OpenTag: An open-source alternative to Claude in Slack — Hacker News · 15 pts
- Show HN: Open Tag, the open source Claude Tag — Hacker News · 4 pts
2 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 260 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 260 GitHub stars; contributors unknown; last commit 0d ago; license MIT.