More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Postman Collection Check

    1

    Marking a Postman variable as "secret" only masks it on screen: export the environment and the API key is in the JSON as plain text.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Postman Collection Check

    Postman Collection Check

    Example session with this skill installed

    Check this project with postman-collection-check.

    • Read your context and instructions
    • Compiled the postman collection check

    $ python3 scripts/check_postman.py examples/risky
    BLOCK bruno/environments/production.bru:3 P04 SECRET_IN_VARIABLES_OR_SCRIPT
    variable apiKey=<redacted, 22 chars>
    Why: A variable with a secret name (token, password, apiKey, client_secret) has a literal value in a Postman environment, globals or collection variable, an Insomnia environment or a Bruno vars block, or a script writes one (pm.environment.set('token', '...')). The Postman type 'secret' only masks the value on screen: it is still written in this file. In Bruno only names listed under vars:secret keep their values out of the file.
    Safer: Leave the shared value empty and set it locally, use Postman Vault ({{vault:name}}), list the name under vars:secret in Bruno or read it from .env ({{process.env.NAME}}), keep exports with values out of git, and rotate the secret.

    BLOCK bruno/orders/create-order.bru:18 P01 SECRET_IN_AUTH
    BLOCK insomnia/shop-insomnia.json:30 P01 SECRET_IN_AUTH
    BLOCK insomnia/shop-insomnia.json:72 P04 SECRET_IN_VARIABLES_OR_SCRIPT
    BLOCK postman/production.postman_environment.json:19 P04 SECRET_IN_VARIABLES_OR_SCRIPT
    BLOCK postman/production.postman_environment.json:25 P04 SECRET_IN_VARIABLES_OR_SCRIPT
    BLOCK postman/shop-api.postman_collection.json:73 P03 SECRET_IN_BODY
    BLOCK postman/shop-api.postman_collection.json:121 P02 SECRET_IN_HEADER_OR_URL
    BLOCK postman/shop-api.postman_collection.json:133 P05 PROVIDER_KEY_OR_PRIVATE_KEY
    BLOCK postman/shop-api.postman_collection.json:206 P01 SECRET_IN_AUTH
    REVIEW bruno/orders/create-order.bru:31 P18 AUTH_HEADER_KEPT_ON_REDIRECT
    REVIEW insomnia/shop-insomnia.json:94 P16 SAVED_TOKEN_OR_SESSION
    REVIEW postman/shop-api.postman_collection.json:24 P17 SCRIPT_LOGS_SECRETS
    REVIEW postman/shop-api.postman_collection.json:56 P16 SAVED_TOKEN_OR_SESSION
    REVIEW postman/shop-api.postman_collection.json:60 P16 SAVED_TOKEN_OR_SESSION
    REVIEW postman/shop-api.postman_collection.json:107 P14 SCRIPT_SENDS_VARIABLES_OUT
    REVIEW postman/shop-api.postman_collection.json:143 P15 PRODUCTION_HOST_IN_REQUEST
    REVIEW postman/shop-api.postman_collection.json:163 P11 PLAIN_HTTP_TO_REMOTE_HOST
    REVIEW postman/shop-api.postman_collection.json:179 P12 TLS_VERIFICATION_OFF
    REVIEW postman/shop-api.postman_collection.json:218 P13 EVAL_IN_SCRIPT

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

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

    About this skill

    Marking a Postman variable as "secret" only masks it on screen: export the environment and the API key is in the JSON as plain text. An OAuth token you fetched can sit in the collection's auth block, and a saved example response can still hold a session cookie, so the next export, fork or git commit ships them. This skill finds those and ten other mistakes in API client files before you share, commit or import them, and tells you how to fix each one.

    Your agent runs a scanner on Postman collections (v2.0 and v2.1), Postman environment and globals exports, Insomnia exports (v4 JSON or YAML, v5 YAML) and Bruno .bru request and environment files. It parses each file to the exact line, treats {{variables}}, {{vault:name}}, {{ _.token }}, {% response %} tags and {{process.env.NAME}} as references rather than secrets, skips the <API Key> style placeholders that OpenAPI imports leave, respects Bruno's vars:secret list, and reads pre-request and test scripts with their comments and strings understood. It never sends a request or runs a script. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • P01: tokens, passwords, client secrets and keys written in auth blocks (bearer, basic, API key, OAuth 2.0 and 1.0, AWS, digest, NTLM, JWT and others)
    • P02: credentials in headers (Authorization, X-API-Key, session cookies), query parameters or user:password@ URLs
    • P03: passwords and secrets in request bodies (raw JSON, form fields, GraphQL)
    • P04: secret-named environment, globals and collection variables with real values, Bruno vars with values written in the file, and scripts that set a literal secret
    • P05: live provider keys and private keys anywhere in the file (GitHub, GitLab, Slack, Stripe live, Google, OpenAI, Anthropic, SendGrid, npm, Hugging Face, Postman API keys)

    REVIEW

    • P11: http:// to remote hosts in requests or base-URL variables
    • P12: strictSSL false, rejectUnauthorized: false or NODE_TLS_REJECT_UNAUTHORIZED
    • P13: eval() or new Function() in pre-request and test scripts
    • P14: scripts that send the whole environment, cookies or a secret to a host the collection does not use (OAuth token requests are recognized)
    • P15: requests hard-coded to a production host instead of {{baseUrl}}
    • P16: saved example responses and cookie jars holding session cookies, JWTs or access tokens
    • P17: console.log of secret variables or whole variable stores
    • P18: Authorization headers kept on redirects to another host (followAuthorizationHeader, forwardAuthorizationHeader)

    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 project (Postman collection and environment, Insomnia export, Bruno request and environment), and the real report the scanner produces on the risky one

    Limits It reads the exported files as written. Values that live only inside the Postman, Insomnia or Bruno app (local values, Postman Vault, Bruno secrets, app-wide settings such as global SSL verification) are not in the files and are not checked. Bruno's YAML format, Postman v1 collections, HAR files and Newman reports are not read, and files over 20 MB are listed as not checked. NOT FLAGGED is not a guarantee.

    Static check of exported collection and environment files. Values kept only inside the API client app and code loaded from script packages 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 files include clearly fake, inert tokens (NOTREAL, EXAMPLE, not-a-real-...) and one labeled sample script that would copy an environment to another host, for the scanner to find. Nothing in them is run.

    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 collection and environment exports as text. It never sends a request or calls the Postman API.

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

    New in APIs & Backend