More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Grafana Config Check

    0

    Check Grafana and Prometheus config before going live: admin/admin, anonymous Admin access, data source passwords in provisioning files, default secret_key, open sign-up, auth proxy without a whitelist, TLS checks off.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Grafana Config Check

    Grafana Config Check

    Example session with this skill installed

    Check this project with grafana-config-check.

    • Read your context and instructions
    • Compiled the grafana config check

    $ python3 scripts/check_grafana.py examples/risky
    BLOCK docker-compose.yml:12 G01 ADMIN_PASSWORD_IN_CONFIG
    - GF_SECURITY_ADMIN_PASSWORD=${GRAFANA_ADMIN_PASSWORD:-admin} (admin is Grafana's default)
    Why: admin_password (or GF_SECURITY_ADMIN_PASSWORD) is set to Grafana's default admin or to a password written in the file. Grafana gives it to the Grafana Admin account when it first creates its database, so admin/admin is the first login anyone tries, and a written password is readable by everyone with the repository.
    Safer: Read it from a file or the environment ($__file{/run/secrets/grafana_admin_password}, $__env{...} or GF_SECURITY_ADMIN_PASSWORD__FILE), use a long random value, and change the admin password of any instance that already started with this one.

    BLOCK docker-compose.yml:14 G02 ANONYMOUS_EDITOR_OR_ADMIN
    BLOCK docker-compose.yml:17 G04 SECRET_IN_GRAFANA_CONFIG
    BLOCK grafana/grafana.ini:15 G04 SECRET_IN_GRAFANA_CONFIG
    BLOCK grafana/grafana.ini:19 G01 ADMIN_PASSWORD_IN_CONFIG
    BLOCK grafana/grafana.ini:47 G04 SECRET_IN_GRAFANA_CONFIG
    BLOCK grafana/provisioning/alerting/contact-points.yml:11 G03 SECRET_IN_PROVISIONING
    BLOCK grafana/provisioning/datasources/datasources.yml:15 G03 SECRET_IN_PROVISIONING
    BLOCK grafana/provisioning/datasources/datasources.yml:21 G03 SECRET_IN_PROVISIONING
    REVIEW docker-compose.yml:15 G14 OPEN_SIGN_UP
    REVIEW grafana/grafana.ini:20 G11 SECRET_KEY_IN_FILE
    REVIEW grafana/grafana.ini:21 G12 COOKIE_NOT_SECURE
    REVIEW grafana/grafana.ini:22 G12 COOKIE_NOT_SECURE
    REVIEW grafana/grafana.ini:23 G13 EMBEDDING_ALLOWED
    REVIEW grafana/grafana.ini:24 G19 BRUTE_FORCE_PROTECTION_OFF
    REVIEW grafana/grafana.ini:27 G14 OPEN_SIGN_UP
    REVIEW grafana/grafana.ini:32 G15 ANONYMOUS_ACCESS
    REVIEW grafana/grafana.ini:37 G16 AUTH_PROXY_WITHOUT_ALLOW_LIST
    REVIEW grafana/grafana.ini:49 G18 TLS_VERIFY_OFF
    REVIEW grafana/provisioning/datasources/datasources.yml:13 G18 TLS_VERIFY_OFF
    REVIEW prometheus/prometheus.yml:14 G17 PROMETHEUS_CREDENTIAL_IN_FILE
    REVIEW prometheus/prometheus.yml:16 G18 TLS_VERIFY_OFF
    REVIEW prometheus/prometheus.yml:23 G17 PROMETHEUS_CREDENTIAL_IN_FILE

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 5 files, 5 with Grafana or Prometheus config 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

    A monitoring stack copied from a demo often ships GF_AUTH_ANONYMOUS_ORG_ROLE=Admin and GF_SECURITY_ADMIN_PASSWORD=${GRAFANA_ADMIN_PASSWORD:-admin} in docker-compose.yml, a data source with its password written in provisioning/datasources/datasources.yml, and the default secret_key that encrypts every stored data source password. Anyone who reaches port 3000 can then edit dashboards, query every data source and read the credentials. This skill finds those and the other common Grafana and Prometheus mistakes before the stack goes live, and tells you how to fix each one.

    Your agent runs a scanner on your project: grafana.ini and custom.ini, GF_* variables of the Grafana service in Docker Compose files, Grafana provisioning YAML (data sources, alert contact points, legacy notifiers, plugin apps) and prometheus.yml. It reads INI files the way Grafana does (; and # comments, """...""" values, the last value wins), so the untouched grafana.ini that Grafana packages ship, with every setting commented out, gives NOT FLAGGED. A value with a $__file{}, $_env{}, $ENV_NAME or ${ENV_NAME} reference anywhere in it (such as Bearer ${LOKI_TOKEN}), or a GF*__FILE variable, counts as kept out of the file, while a written fallback such as ${VAR:-admin} does not. Other YAML in the project, including Helm chart values files, is ignored. It never starts or connects to Grafana or Prometheus. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • G01: admin_password or GF_SECURITY_ADMIN_PASSWORD set to the default admin or to a written password, including a Compose fallback such as ${VAR:-admin}
    • G02: anonymous access with the Editor or Admin role
    • G03: passwords, tokens and keys written in provisioning files: data source password and basicAuthPassword fields, secureJsonData values, contact point secrets, Slack, Discord, Teams and Google Chat webhook URLs, passwords in URLs
    • G04: other credentials in grafana.ini or the Grafana service environment: database and SMTP passwords, OAuth client_secret, cache connection passwords, storage keys, renderer tokens

    REVIEW

    • G11: secret_key written in the file, including Grafana's published default
    • G12: cookie_secure off (or HTTPS without it) and cookie_samesite none or disabled
    • G13: allow_embedding = true
    • G14: open sign-up, and GitHub, GitLab or Google login without an allowed organization, team, group or domain
    • G15: anonymous Viewer access
    • G16: auth proxy without a whitelist
    • G17: Prometheus basic_auth passwords, authorization credentials, bearer tokens and passwords in URLs written in prometheus.yml
    • G18: TLS verification off (insecure_skip_verify, tlsSkipVerify, tls_skip_verify_insecure, skip_verify)
    • G19: brute-force login protection turned off

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example monitoring stack (grafana.ini, docker-compose.yml, data source and contact point provisioning, prometheus.yml), and the real report the scanner produces on the risky one

    Limits It reads each file as written and judges each file on its own. Helm chart values, environment variables set outside Compose files (Kubernetes, systemd, .env files), settings changed in the Grafana UI or SSO settings, ldap.toml, Alertmanager configuration and the contents of files referenced with $__file{} are not seen, so a setting overridden elsewhere can be reported or missed. NOT FLAGGED is not a guarantee.

    Static check of Grafana and Prometheus config text (grafana.ini, custom.ini, Compose GF_* variables, provisioning YAML, prometheus.yml). Grafana's defaults.ini, runtime overrides, the Grafana database and the network around the server are not checked. 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 any payment.

    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 5 days ago

    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 stack includes clearly fake, inert passwords, tokens and a webhook URL (NOTREAL-...) for the scanner to find. It is never started.

    Listed5 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 grafana.ini, provisioning YAML, prometheus.yml and Compose files as text. It never calls Grafana or Prometheus.

    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 Grafana setup, and the real report the scanner prints on the risky example.

    New in DevOps & Cloud