Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Stride Analyzer Skill Pro

    1

    Automated STRIDE threat modeling for repositories and monorepos with evidence-backed remediation plans.

    $8.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Stride Analyzer Skill Pro

    Stride Analyzer Skill Pro

    Example session with this skill installed

    Run a STRIDE analysis on the attached /src directory and docker-compose.yml. We use JWT for auth and store PII in a Postgres container. The frontend is a React SPA.

    • Read your context and instructions
    • Compiled the stride analyzer pro

    Analysis complete. I have evaluated 12 files across the /src directory and the docker-compose.yml manifest. The assessment identified 4 primary threats across Tampering, Information Disclosure, and Elevation of Privilege categories.

    STRIDE Threat Model Report

    Executive Summary

    The scope includes the Node.js backend, React frontend, and Postgres persistence layer. The primary risk theme is the lack of network isolation between the database and the public-facing frontend container, combined with insecure JWT secret handling in environment files.

    Prioritized Findings

    IDSeveritySTRIDE CategoryComponentEvidenceConfidence
    T-01HighTamperingdocker-compose.ymldocker-compose.yml:14High
    I-01CriticalInformation Disclosureauth-servicesrc/auth/config.js:5High
    E-01MediumElevation of Privilegeapi-gatewaysrc/middleware/auth.js:22Medium

    Detailed Threat Analysis

    [I-01] [Critical] — Hardcoded JWT Secret in Source Code
    • STRIDE category: Information Disclosure
    • Affected component: auth-service
    • Evidence: src/auth/config.js:5
    • Observation: The JWT secret is assigned to a constant string directly in the configuration file.

    Threat scenario: An attacker with read access to the repository or an exposed backup can obtain the secret and forge valid administrative tokens.

    • Potential impact: Full takeover of all user accounts and administrative interfaces.
    • Confidence: High (Direct code observation).

    Recommended remediation: Move secrets to an environment variable or a managed secret store (e.g., AWS Secrets Manager).

    • Validation: Ensure config.js uses process.env.JWT_SECRET and verify the secret is not in .env.example.

    Remediation Roadmap

    1. Immediate: Rotate JWT secrets and move to environment variables.

    Near-term: Implement a private network bridge in docker-compose.yml to isolate the Postgres container from the frontend.
    3. Long-term: Implement audit logging for all token generation events to address Repudiation gaps.

    Next steps

    • Provide the src/middleware/auth.js file to verify the JWT expiration logic.
    • Confirm if the Postgres container requires external access for migrations.
    docker-compose.yml

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

    About this skill

    Manual security reviews are slow and often miss structural flaws in complex architectures. This skill automates STRIDE threat modeling by analyzing your code repositories, deployment manifests, and architecture docs to find specific vulnerabilities. It moves beyond generic scanners by mapping trust boundaries and data flows across monorepos and multi-service systems.

    What it does

    • Architectural mapping builds a system model identifying trust boundaries, entry points, and data flows.
    • STRIDE categorization applies Spoofing, Tampering, Repudiation, Information Disclosure, DoS, and Elevation of Privilege frameworks to every component.
    • Evidence-backed auditing extracts file paths and line numbers from source code to prove where vulnerabilities exist.
    • Risk prioritization calculates severity based on impact, exploitability, and existing compensating controls.
    • Remediation planning generates specific code or configuration changes with validation steps for every finding.

    How it works

    1. Context ingestion involves providing repository files, architecture diagrams, or API specs.
    2. System modeling maps how services interact and where sensitive data crosses trust boundaries.
    3. Threat analysis runs the STRIDE framework against the model to identify plausible attack scenarios.
    4. Report generation delivers a prioritized remediation roadmap with file-level evidence and confidence scores.

    Frameworks & tools

    Works with any codebase including monorepos and multi-repository microservices. Compatible with Kubernetes manifests, Terraform IaC, REST/gRPC API specs, and common authentication frameworks.

    Why this beats prompting it yourself

    Generic prompts often hallucinate security flaws or provide vague "best practices." This skill enforces strict evidence requirements, ensuring every finding is tied to an actual file or configuration key while preventing the fabrication of line numbers.

    Use cases

    • Pre-production audits to catch architectural flaws before they are deployed to cloud environments.
    • Monorepo security mapping to visualize how internal packages and dependencies share trust.
    • Compliance preparation by generating the structured threat models required for SOC2 or ISO 27001.

    Known limitations

    Cannot perform dynamic execution, live penetration testing, or active dependency scanning. Accuracy depends on the clarity of supplied architecture docs and source code access.

    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.

    Cannot perform dynamic code execution or live penetration testing. Requires source code or architecture docs for evidence. Does not replace automated SAST/DAST scanners.

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

    Permissions

    Read Files
    Listed20 days ago

    What's inside

    Frequently Asked Questions

    Unlike basic scanners that look for syntax errors, this skill analyzes the structural logic and data flow of your entire system to identify architectural flaws like missing trust boundaries or improper privilege escalation paths.

    The skill is optimized for any LLM-based agent with repository access, and it natively supports diverse environments including Kubernetes manifests, Terraform configurations, and REST/gRPC specifications.

    Yes, the analyzer is specifically designed to map interactions across internal packages and microservices, identifying how data flows across complex, multi-service trust boundaries.

    You will receive the core STRIDE analysis engine, customizable report templates, and a set of integration hooks to connect the skill to your existing CI/CD or documentation workflows.

    Simply provide the skill with access to your source code or architecture manifests; it will automatically begin context ingestion and system modeling without requiring manual rule configuration.

    The skill provides specific file paths, line numbers, and configuration keys for every identified threat, ensuring you have the exact evidence needed to validate and fix the vulnerability.

    New in Security