AxonFlow governance for OpenClaw agents — block dangerous tools, govern MCP access, and keep audit trails for product...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 87/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
OpenClaw
Model
Multiple
Fastest way to find out if axonflow-openclaw-plugin belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/getaxonflow/axonflow-openclaw-plugin && cd axonflow-openclaw-plugin && cat README.mdRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf axonflow-openclaw-pluginNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
./ └─ axonflow-openclaw-plugin/ ← clones here
AxonFlow governance for OpenClaw agents — block dangerous tools, govern MCP access, and keep audit trails for production agent workflows
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 18, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.