surf-agent-skill@9.0.0
Autonomous web research for AI coding agents, on Brave Search and nothing else. The CLI runs the whole loop: an LLM (DeepSeek v4 Pro via OpenRouter) plans the queries, up to --sub-agents of them run at once against Brave — paced to your plan's real rate l
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source confirms automatic global-install setup of first-party agent skills, which warrants a warning under the agent integration policy. The inspected behavior does not establish a concrete attack or justify blocking publication.
Decision evidence
public snapshot- The manifest runs postinstall automatically, while the installer limits system changes to global installs.
- Global postinstall links three package-owned skills into supported agent skill directories and creates an empty Surf key configuration file if absent.
- The project configuration writer is reached through an explicit CLI command and changes only harness timeout settings.
- The plan CLI describes itself as a plan-file and diagnostics helper; no concrete attack behavior was established in the inspected source.
- The inspected installer does not configure agent prompt or tool-content export, and the key file is initialized with blank provider sections.
- The project configuration changes are explicit-command behavior and concern bash timeouts, not agent control or data export.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to surf-agent-skill@9.0.0.
See all versions of surf-agent-skill for other recorded verdicts.
- Review the evidence and your use of surf-agent-skill@9.0.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.