More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Deno Config Check

    1

    Check Deno projects before you ship: -A on start and serve commands, imports over plain http, TLS checks turned off, sh -c built from variables, tokens in Dockerfiles, the lockfile turned off and unpinned remote imports.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Deno Config Check

    Deno Config Check

    Example session with this skill installed

    Check this project with deno-config-check.

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

    $ python3 scripts/check_deno.py examples/risky
    BLOCK Dockerfile:3 D04 SECRET_IN_DENO_CONFIG
    ENV DENO_AUTH_TOKENS=<redacted>
    Why: A token or password is written in the project: DENO_AUTH_TOKENS or DENO_KV_ACCESS_TOKEN with a literal value (Dockerfile ENV, Compose, systemd, scripts), a secret-named variable set in a deno task or Dockerfile, or credentials inside a module URL (a password in the user-info part, or a token in the query). Everyone with the repository or the image can use it.
    Safer: Pass DENO_AUTH_TOKENS and other secrets from the environment or a secret store at run time (BuildKit secret mounts for docker build), never in files or URLs, and revoke the token that was committed.

    BLOCK deno.json:7 D02 TLS_CHECKS_DISABLED
    BLOCK deno.json:13 D01 PLAIN_HTTP_IMPORT
    BLOCK jobs/worker.ts:5 D03 SHELL_COMMAND_WITH_OUTSIDE_DATA
    REVIEW deno.json:5 D11 ALL_PERMISSIONS_GRANTED
    REVIEW deno.json:6 D12 SUBPROCESS_OR_FFI_PERMISSION
    REVIEW deno.json:6 D13 UNSCOPED_WRITE_PERMISSION
    REVIEW deno.json:8 D17 INSPECTOR_ON_NETWORK
    REVIEW deno.json:12 D15 UNPINNED_REMOTE_IMPORT
    REVIEW deno.json:15 D14 LOCKFILE_DISABLED
    REVIEW deno.json:16 D16 ALL_NPM_INSTALL_SCRIPTS_ALLOWED
    REVIEW deno.json:17 D19 DEPENDENCY_AGE_CHECK_OFF
    REVIEW jobs/release.ts:5 D18 SHELL_COMMAND_BUILT_FROM_VALUES

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

    BLOCK deno.json

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

    About this skill

    "start": "deno serve -A main.ts" turns Deno's sandbox off for every dependency your server loads, and one --unsafely-ignore-certificate-errors in a task lets anyone on the network swap the modules Deno downloads. This skill finds those and eleven other Deno configuration mistakes before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on deno.json and deno.jsonc (comments and trailing commas are fine), import maps, deno.lock, package.json scripts, .gitignore, the deno commands in Dockerfiles, Compose files, systemd units, Procfiles and shell scripts, and the imports and Deno.Command calls in your TypeScript and JavaScript. It reads deno commands the way deno does: flags after the script name belong to the script, -qA contains -A, and --allow-run=git is a list while --allow-run is not. Permission findings apply to production commands (start and serve tasks, Dockerfile CMD and ENTRYPOINT, Compose commands, systemd ExecStart, Procfiles, deno compile), not to dev, test, build or --watch tasks. It never runs deno, your tasks or your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • D01: modules loaded over plain http in deno.json imports or scopes, import maps, import statements, deno.lock or deno commands (localhost is fine)
    • D02: --unsafely-ignore-certificate-errors for every host or for hosts other than localhost
    • D03: Deno.Command or Deno.run starting sh, bash, cmd or PowerShell with a command string built from Deno.args, Deno.env, request data or a function parameter
    • D04: DENO_AUTH_TOKENS, DENO_KV_ACCESS_TOKEN and other tokens written in Dockerfiles, Compose, systemd units, tasks and scripts, and credentials inside module URLs

    REVIEW

    • D11: -A / --allow-all on production commands, or "all": true in a deno.json permission set
    • D12: --allow-run without a list or for deno, a shell or an interpreter, and --allow-ffi (flags or deno.json permission sets)
    • D13: --allow-write without a path list
    • D14: "lock": false, --no-lock, or deno.lock ignored in the .gitignore of a Deno project
    • D15: https imports with no version, tag or commit, and jsr: or npm: import-map entries with no version or latest
    • D16: npm install scripts allowed for every package (--allow-scripts with no list, "allowScripts": true)
    • D17: --inspect, --inspect-brk or --inspect-wait bound to 0.0.0.0 or another non-loopback address
    • D18: a shell command string built from other values or held in a variable (a version, a path, a helper's argument)
    • D19: "minimumDependencyAge": 0, which turns off Deno's default 24-hour wait before installing a newly published npm or JSR version

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and official Deno documentation link for each rule
    • A risky and a safe example project, and the real report the scanner produces on the risky one

    Limits It reads each file on its own: a task that calls another task, a permission set chosen with -P, commands run over ssh and values from .env files are not followed, and shell command strings are traced through one variable in the same file only. Unscoped --allow-net, --allow-read, --allow-env and --allow-sys are not reported, because most servers need them and Deno's own Docker examples use them. GitHub Actions workflows, Makefiles and Kubernetes manifests are not read. The official Fresh start task and the Fresh Docker guide use -A and --allow-scripts for every package; these are reported as REVIEW on purpose. 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 Security.

    Static check of config and code text. Tasks that call other tasks, permission sets chosen with -P and commands run over ssh are not followed. 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 5 days ago

    Software
    Git

    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 a clearly fake, inert token (NOTREAL-...) for the scanner to find. Nothing 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 deno.json, deno.lock, Dockerfiles and scripts as text. It never runs deno, a task or any module.

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

    New in Security