Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want agents to work where the task already lives instead of copying context into a separate AI chat workspace.
Who should use it
Who should skip it
Pass on amplifthq/opentag if its scope or audience does not match what your team is building right now.
About this signal
amplifthq/opentag is tracked by RepoRadar as a developer tool in the Agent Workflows section. First seen 2026-06-27; the source record was last checked on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. amplifthq/opentag leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The amplifthq/opentag record combines a 8.5/10 composite score with separate popularity (52.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It can open pull requests, apply labels, or write back into work threads once approvals are granted, so keep the first runner bound to a staging repo or low-risk project; Slack tokens, GitHub credentials, and audit data live in the dispatcher runtime, so treat the runner like operational infrastructure rather than a toy bot; The local versus hosted runner model adds another permission boundary to review before you let it execute on behalf of a team.