I would definitely keep jq dependency there, especially if you plan to expand the code base to provide ecs and Fargate commands. You will quickly run into use cases where JMESpath is not capable of parsing json outputs for different tasksdefintion commands.
If anyone can help with a solution I'd be delighted to remove the dependency on jq.
https://github.com/bash-my-aws/bash-my-aws/blob/b74d92a902bb...