More screenshots
Works with the AI Agents you already use
Spring Boot Config Check
Check Spring Boot application.properties and application.yml before you deploy: hardcoded secrets, Actuator heapdump and env exposed, H2 console on, ddl-auto create-drop, stack traces in errors, and other risky settings.
$5
Spring Boot Config Check
Example session with this skill installed
Check this project with spring-boot-config-check.
- Read your context and instructions
- Compiled the spring boot config
$ python3 scripts/check_spring.py examples/risky
BLOCK application.yml:6 J01 SECRET_IN_CONFIG
spring.datasource.password=<redacted, 19 chars>
Why: A password, secret, token or API key is written in the config file (or as the default of a ${...} placeholder, or inside a database URL), so anyone with the code or the built jar can read it.
Safer: Rotate it, then read it from the environment with no default, for example spring.datasource.password=${DB_PASSWORD}, or from a secrets manager (Vault, AWS, Azure, GCP).
BLOCK application.yml:9 J04 SCHEMA_DROPPED_ON_START
BLOCK application.yml:13 J03 H2_CONSOLE_ON
BLOCK application.yml:27 J02 ACTUATOR_ENDPOINTS_EXPOSED
BLOCK application.yml:36 J01 SECRET_IN_CONFIG
REVIEW application-prod.properties:2 J14 WEAK_TLS
REVIEW application-prod.properties:3 J11 VERBOSE_LOGGING
REVIEW application.yml:10 J11 VERBOSE_LOGGING
REVIEW application.yml:17 J12 ERROR_DETAILS_SHOWN
REVIEW application.yml:21 J13 INSECURE_SESSION_COOKIE
REVIEW application.yml:29 J15 CORS_ALLOWS_ALL_ORIGINS
REVIEW application.yml:32 J16 ACTUATOR_DETAILS_SHOWN
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 2 files, 2 with Spring Boot config 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
Spring Boot settings decide what the outside world can reach: one line exposes Actuator's heapdump endpoint (every secret in memory, downloadable), another drops your tables on every restart (ddl-auto: create-drop). This skill finds those and eight other configuration mistakes before you deploy, and tells you how to fix each one.
Your agent runs a scanner on your application*.properties, application*.yml and bootstrap files. It understands .properties escapes and continuation lines, YAML nesting and lists, multi-document files, profile files (application-prod.yml) and Spring's relaxed names (ddl-auto, ddl_auto and ddlAuto are the same). Dev and test profiles are allowed the H2 console and SQL logging. It never starts your application. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- J01: a password, secret, token or API key in the file, in a ${VAR:default} fallback, or inside a database URL
- J02: Actuator endpoints such as heapdump, env, configprops, shutdown or gateway exposed over HTTP, or '*'
- J03: spring.h2.console.enabled=true
- J04: Hibernate ddl-auto create, create-drop or drop-and-create
REVIEW
- J11: root, Spring, Hibernate or HTTP client logging at DEBUG or TRACE, or show-sql on
- J12: stack traces, exception names or messages in error responses
- J13: session cookie secure or http-only turned off
- J14: TLSv1, TLSv1.1 or SSL allowed, or mail set to trust every certificate
- J15: allowed-origins '*' (Actuator, Spring Cloud Gateway or your own CORS properties)
- J16: Actuator show-details or show-values set to always
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- Risky and safe example config files (YAML, properties and a dev profile), and the real report the scanner produces on the risky ones
Limits It reads the files as written, so environment variables, a config server, @Value defaults and security rules in Java code are not seen. 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 files. Values from environment variables, command-line arguments or a config server are not seen, and each file is checked on its own. 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 config includes a clearly fake, inert password and secret (not-a-real-password, not-a-real-jwt-secret) for the scanner to find.