{"agent":"codex","input":"Audit this Chrome extension for security problems and write security-audit.md. Read public/manifest.json, public/popup.html, public/options.html, src/background.ts, src/content_script.tsx, src/popup.tsx, src/options.tsx, src/sum.ts, webpack/webpack.common.js, webpack/webpack.dev.js, webpack/webpack.prod.js, package.json, package-lock.json, tsconfig.json, jest.config.js, .github/workflows/build.yml and README.md first. Run npm ci, npm run build and npm audit. Start a Chromium with the unpacked dist loaded, note the permission warnings the manifest produces, open a page and confirm the content script runs on it, open the popup and the options page and read their consoles, and send a runtime message from the extension context to show whether the content script checks the sender. Cover the content script's match pattern and host_permissions against what the code needs and whether activeTab would do, the message listener's missing sender check and what it writes into the page, the popup's reading of tab URLs, storage.sync use, the empty service worker loop, the absence of content_security_policy, web_accessible_resources, externally_connectable and minimum_chrome_version keys and what each default means, inline source maps in development builds, and each npm audit advisory judged by whether the package ships in the bundle. For each finding give the severity, the file and line, the check that showed it and the fix. Do not paste any secret. Change no code.","resources":[{"url":"https://github.com/your-org/your-app"}]}