Agent Tool 0.6.0

Changed

• Repository archives are fetched as tar.gz and unpacked through the same reader the browser extension already used, so the extension now ships with no runtime dependencies and one archive format instead of two.
• The one-time restore of tools disabled by version 0.4.0 has been removed. If you still have such tools, install 0.5.0 once before upgrading, or move them out of the extension's disabled-skills / disabled-agents folders by hand.
• The detection card in the browser extension keeps its entrance animation but no longer draws the sparkle marks beside it.

Fixed

• A GitHub /blob/ URL that points at a directory (GitHub itself redirects these to the /tree/ view) is now read as a directory, so Skills published that way resolve to the right name and path instead of failing verification.

Added

• The browser extension can now detect Skills and Subagents on an unsupported site automatically, one site at a time. After it actually confirms a tool on a page, the popup offers Enable for this site; allowing it grants access to that single origin — never subdomains, never all sites — and Agent Tool then checks pages on that site as you browse. Automatic detection resolves what it can on its own and verifies against GitHub; a page it cannot resolve goes through the same single Jev question the manual scan asks, so it needs AI-assisted detection enabled and is capped per hour (only a counter is stored for that, never the sites you visited). Sites you allowed are listed under Settings → Automatic detection, read back from the browser's own permission API, and removing one stops detection immediately. Navigations on sites you have not allowed never reach the extension.
• Beta: the browser extension can optionally use a user-supplied Jev API key to manually inspect an unsupported page for a GitHub-backed Skill or Subagent. It uses temporary activeTab access, sends only minimized candidate evidence to TypeSafe with key-like values redacted, and still requires the existing GitHub verification before showing an install candidate. Which tool to install is decided locally by matching the page's own URL against the links it carries — Jev is only asked whether the page ships a tool at all, and only when no direct link is found. A page that lists several tools tells you to open the one you want instead of guessing, and a #fragment in the URL scopes the scan to the entry you are reading.