More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Spring Boot Surface Audit

    1

    Generates a verifiable, tool-driven inventory of Spring Boot endpoints, mappers, and microservice dependencies.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Spring Boot Surface Audit

    Spring Boot Surface Audit

    Example session with this skill installed

    We keep getting 404s since the gateway rewrite. Audit ~/work/mall-swarm and tell me the path
    clients actually call for each endpoint — not just the annotation path. I also need to know which
    module calls out to which, and anything you can't determine from source.

    • Read your context and instructions
    • Compiled the spring boot surface
    1. De-duplicate the 7 colliding paths...
    2. Decide about discovery.locator...
    3. Re-run after the fix. The collision count is the regression test...

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

    About this skill

    Auditing a large Spring Boot or Spring Cloud repository by hand is slow and prone to error. Grep misses inherited handlers, conditional endpoints, and broken Feign contracts. This skill provides a verifiable, tool-driven inventory of the entire API surface and persistence layer.

    What it does

    • Inventory HTTP surface by listing every controller, verb, and path across all modules.
    • Trace outbound edges to identify Feign clients and Spring Cloud Gateway routes.
    • Audit persistence layer to map XML, annotation, and JPA mappers while flagging orphan XML files.
    • Perform cross-checks to find routes pointing at nothing or stale Feign client contracts.
    • Identify unresolved paths that rely on configuration, ensuring no hidden endpoints are missed.

    How it works

    1. Scope the repository by listing projects and modules to understand inter-module dependencies.
    2. Index endpoints and mappers using specialized tools to extract counts and locations for every controller and statement.
    3. Verify infrastructure by cross-referencing gateway prefixes against actual controller paths.
    4. Generate the audit in a structured Markdown report including a full appendix of the tool calls used for the data.

    Frameworks & tools

    Requires the spring-mcp MCP server. Built for Java and Kotlin Spring Boot and Spring Cloud projects.

    Why this beats prompting it yourself

    Standard prompts rely on file-by-file reading which misses inherited methods and cross-module route resolution. This skill uses specific MCP tools to pull actual Spring metadata, ensuring every count and path is accurate and reproducible.

    Use cases

    • Onboard to a codebase by generating a complete map of an unfamiliar microservice.
    • Pre-migration review to catalog all endpoints before a major framework or version upgrade.
    • Security surface audit to find unmapped controllers or conditional endpoints that might bypass simple checks.
    • Refactoring cleanup to locate orphan XML mappers and dead Feign client definitions.

    Known limitations

    Does not track RestTemplate or WebClient calls. Only supports Spring frameworks; non-Spring web frameworks like Quarkus or JAX-RS will result in empty endpoint reports.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Requires the free spring-mcp MCP server and JDK 21+ (see INSTALL.md).

    Reads source only — never starts the app, so Actuator endpoints, runtime-registered mappings
    and AOP proxy targets are reported as "not determined", not guessed.

    Outbound edges cover @FeignClient and Spring Cloud Gateway only; RestTemplate, RestClient and
    WebClient calls are invisible.

    Non-Spring frameworks (Solon, JAX-RS, Quarkus) are out of scope.

    Global path prefixes that come from configuration are reported as a warning, not resolved into
    URLs.

    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 13 days ago

    Permissions

    Terminal / Shell
    Read Files
    Environment Variables

    File Scopes

    **/*.java
    **/*.kt
    **/*.xml
    **/pom.xml
    **/build.gradle*
    **/application*.yml

    Read-only. The preflight script runs `java -version`, checks that a jar exists, and reads JAVA_HOME to locate the JDK. No file writes, no network access. The analyzer reads project source only.

    Listed13 days ago

    What's inside

    Frequently Asked Questions

    This skill uses the `spring-mcp` server to extract precise Spring metadata, allowing it to trace inherited methods, cross-module dependencies, and hidden XML mappers that standard LLM file-reading often misses.

    It is specifically designed for Java and Kotlin projects using Spring Boot and Spring Cloud; please note that other frameworks like Quarkus or JAX-RS are not currently supported.

    You will need to have the `spring-mcp` server installed and configured in your environment to allow the AI agent to execute the necessary indexing and verification tools.

    The skill produces a structured Markdown audit report detailing your entire HTTP surface, persistence layer maps, and an appendix of the tool calls used for verification.

    While it is highly effective at mapping Feign clients and Gateway routes, it does not currently track manual `RestTemplate` or `WebClient` calls.

    New in LLM Ops