Any ad-blocker or otherwise page-modifying Chrome Extension requires the same permissions and likely does the same thing.
Provided the GoLinks extension isn't phoning home with the full contents of the pages its parsing, and immediately discards non-GoLink related data, this shouldn't be a problem.
It would be nice if the GoLinks team could clarify exactly what data is sent back to their servers by the Chrome Extension.
Chrome Extensions can also be inspected and their network traffic can be sniffed quite easily, so independent auditing is possible as well.
I suggest adding an alert anytime a new version of the extension is published, or if you already get an email from Chrome Web Store each time a new extension is published or the email addresses of the Chrome Web Store account are changed (npm does this I believe), to make sure it gets sent to an inbox that's actively monitored.
Based on what we're hearing from the comments, we're planning to roll out a more detailed privacy page to build more confidence with our users.