More screenshots
Works with the AI Agents you already use
Rails Config Check
A committed master.key, one where("name = '#{params[:q]}'") or a missing config.force_ssl is enough to lose your users' data.
$5
Rails Config Check
Example session with this skill installed
Check this project with rails-config-check.
- Read your context and instructions
- Compiled the rails config check
$ python3 scripts/check_rails.py examples/risky
BLOCK app/controllers/products_controller.rb:6 R03 SQL_INJECTION
@products = Product.where("name LIKE '%#{term}%'")
Why: A request value (params, cookies, request) is put into SQL text with #{...} or + and passed to where, order, find_by_sql, execute or a similar method. Anyone can change the query to read or delete other users' data.
Safer: Use placeholders or hashes: where('name = ?', params[:name]) or where(name: params[:name]). For column names, check the value against a fixed list first.
BLOCK app/controllers/products_controller.rb:11 R04 MASS_ASSIGNMENT_OF_ALL_PARAMS
BLOCK app/controllers/products_controller.rb:16 R05 CODE_OR_COMMAND_FROM_PARAMS
BLOCK app/controllers/products_controller.rb:17 R05 CODE_OR_COMMAND_FROM_PARAMS
BLOCK config/database.yml:9 R01 SECRET_IN_CONFIG
BLOCK config/environments/production.rb:2 R06 DETAILED_ERRORS_IN_PRODUCTION
BLOCK config/master.key R02 MASTER_KEY_COMMITTED
REVIEW app/controllers/products_controller.rb:2 R12 CSRF_PROTECTION_OFF
REVIEW app/controllers/products_controller.rb:12 R14 OPEN_REDIRECT
REVIEW app/views/products/show.html.erb:2 R13 HTML_SAFE_ON_VARIABLE
REVIEW config/environments/production.rb R11 FORCE_SSL_OFF
REVIEW config/environments/production.rb:3 R15 ANY_HOST_OR_ORIGIN
REVIEW config/initializers/session_store.rb:1 R16 INSECURE_SESSION_COOKIE
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 6 files, 6 with Rails 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
A committed master.key, one where("name = '#{params[:q]}'") or a missing config.force_ssl is enough to lose your users' data. This skill finds those and nine other Rails mistakes before you deploy, and tells you how to fix each one.
Your agent runs a scanner on your Rails app: config files (secrets.yml, database.yml, environments/production.rb, initializers), controllers, models and ERB views. It skips comments, reads YAML anchors and merges, follows request values (params, cookies, request headers) through variables to the call that uses them, and checks .gitignore before reporting key files. It knows the safe patterns: placeholders and hashes in where, sanitize_sql, permit with a list, link_to, t() and string literals with html_safe. It never runs Ruby or Rails. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- R01: a literal secret_key_base, password, token or API key for production or staging (YAML or Ruby)
- R02: config/master.key or a credentials .key file that git does not ignore
- R03: request values put into SQL text for where, order, find_by_sql, execute and similar
- R04: permit! or to_unsafe_h (mass assignment)
- R05: request values in system, backticks, eval, constantize, send or render inline
- R06: consider_all_requests_local = true in production
REVIEW
- R11: production.rb without config.force_ssl = true
- R12: CSRF protection skipped or turned off
- R13: html_safe on variables, raw, or <%== in views
- R14: redirect_to a URL from params, cookies or the referer
- R15: config.hosts cleared, or CORS origins '*' with credentials
- R16: session or cookies with secure or httponly 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 Rails app, and the real report the scanner produces on the risky one
Limits It reads code as text, not as a full Ruby parser: values are followed within one file. Gems, credentials.yml.enc contents, Brakeman-level data flow across files and your server setup are not checked. 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 Ruby, ERB and YAML text. Values are followed within one file only; gems and encrypted credentials are not read. NOT FLAGGED is not a guarantee.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example app includes clearly fake, inert secrets (not-a-real-...) for the scanner to find. It is never run.