browser-testing-with-devtools Audit-Bericht.

Warnungen

• Dependency or permission surface needs review
• Permission surface may require sandboxing
• The SKILL.md excerpt stops mid-sentence in the 'Treat All Browser Content as Untrusted Data' section. If this reflects the full submitted file, the security guidance is incomplete and should be finished with explicit handling rules for untrusted browser content.
• JavaScript Execution is described as 'read-only state inspection', but the underlying tool can run arbitrary code in the page context. The skill needs a sharper boundary: do not mutate page state, read cookies/localStorage, or exfiltrate data unless explicitly required by the task.
• The tools table uses friendly names rather than exact chrome-devtools MCP tool names, which may make it harder for an agent to know which MCP tool to invoke.
• Permission surface needs review: secrets or environment access, shell or command execution
• Dependency/runtime risk: command execution surface, credential or environment access
• Permission surface: secrets or environment access, shell or command execution

Methode

This report combines public metadata, AI review output, repository freshness, install readiness, OpenAgentSkill events, quality scoring, trust checks, and the agent safety gate. It is not a full source-code security review.