Operations · Intermediate

Verified

Automated verification

  • Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
  • Drafting model not recorded.
  • Second-model review: kimi-code/k3.1-pro (no critical or high findings).
  • Verified .
  • Automated checks and AI review only, not human review.
How verification works

Vet third-party AI tool packages before installation

Compare declared capabilities with actual files and probe risky servers.

Use with BotBento

Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.

  1. When something happensNew tool package submitted
  2. ThenInspect files and probe server
  3. ResultRisk report with approval gate

A bot reviews an AI tool package or server repository before adoption. It maps declared features and permissions, inspects files and configuration for mismatches, runs the server in a controlled probe where possible, and produces a plain-language risk report. Nothing is installed or connected until the user approves.

Quick answers

What does it do?

Compare declared capabilities with actual files and probe risky servers. Result: Risk report with approval gate.

What does it need?

Tools: GitHub, Terminal, Docs. Intermediate: some setup. The prompt includes an approval step.

How do I run it?

When something happens: New tool package submitted. Copy the prompt below into a bot in BotBento.

Prompt to start with

BotBentoRecommended
When a new package is submitted, read its declared capabilities and permissions. Compare them with the repository files and configuration. Run the server only in an isolated probe and record its observed behavior. Flag mismatches, unclear claims, and risky access. Write a short risk report with evidence and recommended next steps. Ask for approval before installing, connecting to tools, sending messages, making payments, or deleting anything.