More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Ruby Gemfile Check

    1

    This skill finds those and nine other Bundler mistakes before your next bundle install, and tells you how to fix each one.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Ruby Gemfile Check

    Ruby Gemfile Check

    Example session with this skill installed

    Check this project with ruby-gemfile-check.

    • Read your context and instructions
    • Compiled the ruby gemfile check

    $ python3 scripts/check_gemfile.py examples/risky
    BLOCK .bundle/config:4 G03 CREDENTIALS_IN_BUNDLE_CONFIG
    BUNDLE_GEMS__EXAMPLE__COM: "<redacted>"
    Why: The project's .bundle/config holds gem server or git credentials (for example BUNDLE_GEMS__EXAMPLE__COM: "user:password") and .gitignore does not ignore it, so it is committed with the code. Bundler's guides say not to check in the .bundle folder.
    Safer: Add /.bundle to .gitignore, remove the file from the repository, revoke the credentials, and set them per machine with bundle config set --global or as BUNDLE_... environment variables in CI.

    BLOCK .bundle/config:5 G01 INSECURE_GEM_SOURCE
    BLOCK Gemfile:2 G01 INSECURE_GEM_SOURCE
    BLOCK Gemfile:12 G02 CREDENTIALS_IN_SOURCE_URL
    BLOCK admin/Gemfile:9 G01 INSECURE_GEM_SOURCE
    BLOCK admin/Gemfile.lock:2 G01 INSECURE_GEM_SOURCE
    BLOCK admin/Gemfile.lock:9 G02 CREDENTIALS_IN_SOURCE_URL
    REVIEW .bundle/config:6 G18 GEM_CHECKSUMS_NOT_CHECKED
    REVIEW Gemfile G13 NO_COMMITTED_LOCKFILE
    REVIEW Gemfile:2 G12 MULTIPLE_GLOBAL_SOURCES
    REVIEW Gemfile:16 G11 GIT_GEM_NOT_PINNED
    REVIEW Gemfile:18 G15 PATH_GEM_OUTSIDE_PROJECT
    REVIEW Gemfile:20 G16 UNPINNED_BUNDLER_PLUGIN
    REVIEW admin/Gemfile:4 G17 GIT_TOKEN_WRITTEN_TO_LOCKFILE
    REVIEW admin/Gemfile.lock G18 GEM_CHECKSUMS_NOT_CHECKED
    REVIEW engines/billing/billing.gemspec:12 G14 GEMSPEC_DEPENDENCY_WITHOUT_VERSION
    REVIEW engines/billing/billing.gemspec:13 G14 GEMSPEC_DEPENDENCY_WITHOUT_VERSION

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

    source "https://deploy:password@gems.example.com" puts your gem server password in every clone of the repository, and a git_source with "https://#{ENV["GITHUB_TOKEN"]}@github.com/..." looks safe until Bundler writes the real token into Gemfile.lock. This skill finds those and nine other Bundler mistakes before your next bundle install, and tells you how to fix each one.

    Your agent runs a scanner on your Gemfiles (Gemfile, gems.rb, Gemfile.next, gemfiles/*.gemfile), Gemfile.lock, .gemspec files and the project's .bundle/config. It skips Ruby comments, follows #{...} inside strings, knows Bundler's github:, gist:, bitbucket: and git_source shorthands and its source, git and path blocks, tells an application from a gem, and reads .gitignore so an ignored .bundle/config or Gemfile.lock is judged correctly. It never runs Ruby or Bundler. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Passwords and tokens are never printed.

    What it checks

    BLOCK

    • G01: gem sources, mirrors and git gems over http:// or git://, and ssl_verify_mode 0
    • G02: passwords and tokens in source or git URLs, in a Gemfile, a gemspec or Gemfile.lock
    • G03: gem server credentials in a .bundle/config that .gitignore does not ignore

    REVIEW

    • G11: git and github gems without ref: or tag:, or with a ref that can move (a branch name)
    • G12: more than one global source line (dependency confusion; Bundler 4 refuses such a Gemfile)
    • G13: an application without a committed Gemfile.lock
    • G14: gemspec runtime dependencies without a version
    • G15: path gems outside the project
    • G16: Bundler plugins without an exact version
    • G17: tokens from ENV in git URLs, which Bundler copies into Gemfile.lock
    • G18: gem checksum checks turned off in .bundle/config, or a Bundler 4 lockfile without a CHECKSUMS section

    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 (an app, an admin app and a billing engine, with Gemfiles, lockfiles, a gemspec and .bundle/config), and the real report the scanner produces on the risky one

    Limits It reads each file as written: values from the environment are not resolved, ~/.bundle/config, BUNDLE_ environment variables and CI settings are not read, and gem servers are not contacted. Rails settings and application code are not checked. NOT FLAGGED is not a guarantee.

    Static check of Gemfile, Gemfile.lock, gemspec and .bundle/config text. Environment variables, global Bundler settings and the gem servers themselves 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

    Requires

    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 clearly fake, inert passwords and tokens (NOTREAL-...) for the scanner to find. Nothing is installed.

    Listed5 days ago
    Updated4 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 Gemfile, Gemfile.lock and gemspecs as text. It never runs Bundler or downloads gems.

    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.

    New in Security