More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Vector Database Config Check

    1

    Any one of these leaves every document you indexed open to whoever finds the port.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Vector Database Config Check

    Vector Database Config Check

    Example session with this skill installed

    Check this project with vector-database-config-check.

    • Read your context and instructions
    • Compiled the vector database config

    $ python3 scripts/check_vectordb.py examples/risky
    BLOCK app/milvus_store.py:4 V04 MILVUS_DEFAULT_ROOT_PASSWORD
    client = MilvusClient(uri="https://milvus.acme-support.io:19530", token="<redacted>")
    Why: Milvus creates the root user with the published password Milvus, and this code or connection setting logs in as root:Milvus to a public host (a public IP or internet domain). The server still has the default superuser password, so anyone on the internet who has read the Milvus docs can log in as root.
    Safer: Set common.security.defaultRootPassword from a secret before the first start (or change it with update_password right after), give the app its own user with only the privileges it needs, and read that user's token from the environment.

    BLOCK app/search.py:6 V03 SECRET_IN_CONFIG_OR_CODE
    BLOCK docker-compose.yml:9 V03 SECRET_IN_CONFIG_OR_CODE
    BLOCK docker-compose.yml:16 V02 AUTH_SETTING_HAS_NO_EFFECT
    BLOCK docker-compose.yml:28 V02 AUTH_SETTING_HAS_NO_EFFECT
    BLOCK docker-compose.yml:30 V03 SECRET_IN_CONFIG_OR_CODE
    BLOCK docker-compose.yml:32 V03 SECRET_IN_CONFIG_OR_CODE
    BLOCK docker-compose.yml:40 V02 AUTH_SETTING_HAS_NO_EFFECT
    BLOCK k8s/weaviate.yaml:35 V01 UNAUTHENTICATED_DB_EXPOSED
    REVIEW app/reindex.py:4 V17 MILVUS_DEFAULT_ROOT_PASSWORD_KEPT
    REVIEW app/search.py:5 V12 NO_TLS_TO_REMOTE_HOST
    REVIEW deploy/weaviate-readers.env:6 V14 BROAD_ACCESS_LIST
    REVIEW docker-compose.yml:14 V15 UNPINNED_IMAGE
    REVIEW docker-compose.yml:18 V11 NO_AUTH_PORT_PUBLISHED
    REVIEW docker-compose.yml:19 V16 INTERNAL_PORT_PUBLISHED
    REVIEW docker-compose.yml:42 V13 RESET_API_ENABLED
    REVIEW docker-compose.yml:44 V11 NO_AUTH_PORT_PUBLISHED

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 6 files, 6 with vector database content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    BLOCK docker-compose.yml

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Qdrant ignores QDRANT_API_KEY on the server (it reads only QDRANT__SERVICE__API_KEY), a Weaviate config that adds API keys but leaves anonymous access set to 'true' still lets anyone in, and Docker publishes "6333:6333" on every interface. Any one of these leaves every document you indexed open to whoever finds the port. This skill finds those and the other vector database mistakes below before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on Docker Compose files, Kubernetes manifests, Helm values for the Weaviate, Qdrant and Milvus charts, Qdrant, Milvus and Chroma server configs, .env files, and Python, JavaScript and TypeScript client code (including Pinecone clients and LangChain and LlamaIndex vector stores). It knows each server's real setting names and defaults, treats ${VAR} references and Kubernetes secretKeyRef values as configured, gives local quickstart Compose files REVIEW rather than BLOCK, and never connects to a database. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • V01: a database whose missing authentication the file shows, behind a public LoadBalancer (Kubernetes Service or Helm values)
    • V02: authentication the server ignores: Weaviate anonymous access left on beside API keys, anonymous admins, switches set to 'yes', QDRANT_API_KEY on the Qdrant container, legacy auth settings on Chroma 1.x
    • V03: API keys, passwords and tokens written in Compose, Kubernetes, Helm values, server configs, settings modules or client code, including Weaviate module keys such as OPENAI_APIKEY (SOPS-encrypted values are skipped)
    • V04: the default Milvus root login (root with the password Milvus) sent to a public host

    REVIEW

    • V11: an unauthenticated database port published on every interface, a load balancer whose scope is unclear, or Helm values that rely on the chart's default of no authentication
    • V12: plain HTTP or certificate checks turned off when connecting to a remote database
    • V13: Chroma's reset endpoint turned on
    • V14: anonymous read access, or every API key user an admin, in Weaviate
    • V15: database images on a moving tag (latest-style or no tag)
    • V16: Qdrant's cluster port 6335 or Weaviate's profiling port 6060 published
    • V17: the default Milvus root password probably still in use (root:Milvus to an internal host, or authorization turned on without a new root password)

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and official source for each rule
    • A risky and a safe example RAG project (Compose, Kubernetes, .env and Python), and the real report the scanner produces on the risky one

    Limits It reads each file on its own: a Kubernetes Service is matched only with workloads in the same file, Helm templates are not rendered, and files named by env_file or mounted as server config are not opened, so auth set there counts as unknown. A host counts as remote when it is a public IP or ends in a public top-level domain. Ingress authentication, network policies and cloud firewalls are not known, and Dockerfiles, notebooks and Terraform are not read. NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Static check of config and code text. Helm templates are not rendered, files named by env_file or mounted as server config are not opened, and ingress authentication, network policies and cloud firewalls are not known. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Software
    Python

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert keys (not-a-real-...) for the scanner to find. Nothing in it is run.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads your configs and client code as text. It never connects to Qdrant, Weaviate, Chroma or Milvus.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example vector database setup, and the real report the scanner prints on the risky example.

    New in LLM Ops