Turns any OpenAPI/Swagger API into an CLI with set of commands. One CLI command per endpoint.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health 42/100. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
OpenClaw
Model
Multiple
Fastest way to find out if openapi-to-cli belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/EvilFreelancer/openapi-to-cliRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/EvilFreelancer/openapi-to-cliNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ openapi-to-cli/ ← installs here └─ settings.json
Turns any OpenAPI/Swagger API into an CLI with set of commands. One CLI command per endpoint.
Source: GitHub repository
Source check: August 18, 2026
Upstream commit: August 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.