Maton browse plan — API Gateway

This skill largely does what it says, but there are a few things to check before installing: 1) The skill declares MATON_API_KEY (needed to call Maton services) but the instructions also use MATON_RELAY_TOKEN for the local relay — expect to provide that token separately (it is not declared). 2) The build steps run npm install and npm run build in the repo you clone; inspect package.json and any install/postinstall scripts to ensure you trust the code before running. 3) The optional 'install-native-host' step registers a native messaging host on your machine (writes OS/browser config, may require elevation) — only run it if you understand and consent to that change. 4) The exported matonPlan contains browsing-origin summaries and resource URLs (sensitive browsing-derived data); confirm what of that data will be transmitted to Maton endpoints when the agent compares/suggests connectors. 5) If you want the agent to access the local relay using MATON_RELAY_TOKEN, explicitly set that env var only in a trusted context (avoid sharing it in multi-tenant environments). If you need greater assurance, ask the skill author for explicit documentation that lists all env vars used, the exact network endpoints called, and the exact data sent to Maton services.