Agent Tool 0.2.0

Added

• Tools installed by the browser extension are picked up by the IDE extension on its next scan, so they can be removed, disabled, and updated from the Dashboard like anything else.
• Registry entries whose files are gone are dropped on the next scan, so the list no longer shows tools that were deleted outside Agent Tool.
• A browser extension for Chrome, Edge, and Brave that spots skills and subagents while you browse GitHub, skills.sh, and agentsdirectory.dev, and installs them into Claude Code, Cursor, or Codex. It writes only to folders you pick, and works without the IDE extension installed.
• Opening a folder that holds several skills — github.com/<owner>/<repo>/tree/<branch>/skills, or a repository page on a catalog — lists them in the browser extension with an install button per row, so they go in one at a time rather than all together. Each one is fetched file by file instead of as an archive, so skills can be installed from repositories whose archive is over the download limit (measured: 104 KB taken from a repository whose archive is 116 MB).
• A Supported sites dialog in the browser extension with links to GitHub and every supported catalog.
• A light / dark / system theme setting in the browser extension's popup.
• A unified release/Ver_<semver> workflow that gives both extensions the same version, packages and checksums their artifacts, and attaches them to one GitHub Release, plus a privacy policy (PRIVACY.md) and a Chrome Web Store listing checklist (docs/browser-store-listing.md).
• Conditional Chrome Web Store submission from that workflow, skipped until all of its required GitHub Secrets are configured; submit the approved zip to Edge Add-ons manually.
• The browser extension's popup explains what happens before it writes: which folder the item goes into, that your browser only reveals the folder's name rather than its full path, that the source resolves to a public GitHub repository, and that unsafe archive paths and links are refused.

Changed

• Installing stops before anything is deleted when the download contains a name no file system can take (Windows device names, <>:"|?*, trailing dots), instead of failing halfway through and leaving neither the old nor the new version.
• Registry entries are kept, not dropped, when a scanned folder cannot be read, so a temporary permission or sync problem no longer loses pinned and disabled state. The unreadable folder is reported instead.
• Installing over an existing Skill now replaces it instead of writing on top of it, so files that only existed in the previous version no longer linger. The old copy is removed only after the new one has been fetched.
• The browser extension's popup uses a palette matching the extension icon, with a few short, prefers-reduced-motion-aware animations (the detected-card entrance, the install spinner, the dialog open).
• The browser extension no longer asks for the unlimitedStorage permission. It keeps only a small amount of data (the folder handles you granted and the list of what it installed), which fits in the ordinary extension storage quota.
• Installing over an existing item stops instead of replacing it when that item is over 64 MB, because the old copy is held in memory so it can be put back if the replacement fails. Nothing is deleted, and the message says to remove the item yourself or pick another destination.

Fixed

• Installing from a catalog link no longer holds the whole repository in memory while it looks for the skill. The conventional skills/<name> location is checked first with a single request, and when it matches only that folder is read (measured: 51.2 MB down to 2.7 KB for one entry). Catalogs whose name differs from the folder fall back to the previous behaviour.
• A skill whose repository archive is over the download limit can now be installed from its own page: when the archive is refused, the files are fetched individually instead (measured: 104 KB taken from a repository whose archive is 116 MB). Repositories whose archive works are unaffected.
• A repository listing that could not be read is no longer reported as "not found". Hitting GitHub's unauthenticated request limit now reads as a fetch failure, which is what it is.
• Choosing a folder in Brave reported what went wrong instead of doing nothing: Brave turns the File System Access API off by default, and the extension now says so and walks through enabling it in brave://flags.
• The "Installed here" list drops entries that were removed from the IDE extension. It could not read the folder to check, so it kept showing them.
• The browser extension's dropdown menus and dialogs stay legible in dark mode; some text could render unreadable against the page's own dark styling before.
• A Skill whose folder contains a symbolic link is no longer offered for install by the IDE extension. Symlinks are never extracted, so installing one produced a copy with files silently missing.
• Pasting a link that is not a skill or subagent says so in the browser extension. The message was wired up but its visibility was inverted, so nothing appeared.
• The browser extension's "paste a URL" label no longer folds the "Supported sites" link into the input's accessible name, the install-succeeded banner is announced to screen readers and keeps focus while visible, and the URL error message is now associated with its field.