Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Wazuh Fullstack AI

    1

    Deploy and manage a full Wazuh security stack with local AI alert analysis and automated Windows agent orchestration.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Wazuh Fullstack AI

    Wazuh Fullstack AI

    Example session with this skill installed

    Inspect my current Wazuh stack and analyze the latest alert from the fixtures folder.

    • Read your context and instructions
    • Compiled the wazuh fullstack ai

    I have completed the stack inspection and processed the requested alert. The stack is healthy, though the agent connection is currently idle.

    Stack Status & Alert Analysis

    ComponentStatusDetails
    Docker ContainersUPManager, Indexer, and Dashboard are running
    Wazuh APIACTIVEResponding on port 55000
    Windows AgentRUNNINGWazuhSvc is active (PID: 4820)
    Local AI (Laya)READYONNX provider initialized
    Local AI (Ollama)READYModel qwen2.5:7b loaded

    Alert Triage Result: alert_20231012_01.json

    • Decision: CRITICAL
    • Confidence: 0.94
    • Routing: Sent to Ollama for summarization

    Summary: Multiple failed RDP login attempts detected from IP 192.168.1.45 targeting the Administrator account. This indicates a potential brute-force attack.

    Recommendation: Validate if this IP belongs to an authorized user. If not, consider blocking the IP at the firewall level and enforcing MFA for RDP sessions.

    Next steps

    1. Review the detailed incident entry in wazuh-incidents.db.
    2. Execute connect-agent-manager.ps1 if you need to refresh the agent's connection strings.
    3. Run inspect-stack.py again after any network configuration changes.

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

    About this skill

    Managing a security operations stack requires constant switching between infrastructure management, agent configuration, and alert triage. This skill automates the lifecycle of a Wazuh full-stack environment, integrating local AI to filter and summarize security events without sending sensitive data to the cloud.

    What it does

    • Automated Stack Deployment installs the Wazuh manager, indexer, and dashboard using Docker via PowerShell scripts.
    • Hybrid AI Alert Triage utilizes a two-tier pipeline with Laya/ONNX for fast noise filtering and Ollama for detailed summarization.
    • Secure Agent Provisioning connects Windows agents to the manager with mandatory configuration backups and auto-restoration.
    • Stack Inspection performs multi-layer health checks across Docker, the Wazuh API, and agent services to diagnose connectivity gaps.
    • Incident Logging records critical alerts and stack changes into a local SQLite database for auditability.

    How it works

    1. Run Inspection using inspect-stack.py to establish the current state of Docker containers, services, and AI models.
    2. Execute Deployment with install-manager-docker.ps1 using the --dry-run flag to review the plan before giving the final execution command.
    3. Connect Agents by running the connection script which handles protocol negotiation and ossec.conf updates.
    4. Process Alerts through the automated pipeline which routes JSON events to local models for classification and summary.

    Frameworks & tools

    The skill utilizes Docker for containerized infrastructure and PowerShell for Windows host management. The AI pipeline runs locally via Ollama (qwen2.5:7b) and Laya/ONNX, storing data in SQLite and SiYuan.

    Why this beats prompting it yourself

    Manual Wazuh orchestration often leads to broken agent-manager protocols and inconsistent alert handling. This skill enforces mandatory dry-runs, automated backups, and a resource-efficient AI routing logic that prevents high GPU usage on low-priority noise.

    Use cases

    • Deploying a local SOC environment for testing or small-scale production.
    • Automating the triage of high-volume security alerts using local LLMs.
    • Diagnosing why a Windows endpoint is not appearing as "Active" in the dashboard.
    • Maintaining an append-only audit log of all infrastructure changes.

    Known limitations

    Does not perform automatic remediation like IP blocking or process isolation. Requires elevated privileges for Windows service management and specific PowerShell syntax handling for Docker.

    No auto-remediation (suggestions only). Requires elevated privileges for ossec.conf. Docker scripts require PowerShell 5.1 compatibility. AI summary requires local GPU/Ollama.

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

    Requires

    Python 3.10+
    PowerShell 5.1+
    Docker Desktop
    Ollama (optional)
    Laya/ONNX (optional)Python
    Git
    Python

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    This skill operates entirely on localhost. It reads its own scripts/references/fixtures and modifies ossec.conf with mandatory backup before any change. No cloud calls, no telemetry. Docker is used for Wazuh deployment. Ollama and Laya are optional local AI providers.

    Listed29 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the deployment of the Wazuh manager, indexer, and dashboard via Docker, while providing specialized scripts for secure Windows agent provisioning and health monitoring.

    The skill uses a local-first AI approach with Ollama and ONNX, ensuring all security alerts are analyzed on your hardware without sending sensitive log data to external cloud providers.

    Yes, the skill is designed for Windows-centric environments, utilizing PowerShell for host management and requiring elevated permissions to handle service configurations and Docker containers.

    You receive the complete orchestration logic, including PowerShell deployment scripts, the dual-tier AI processing pipeline, health inspection tools, and a local SQLite logging system.

    Unlike a simple prompt, this skill includes built-in safety features like mandatory dry-runs, automatic configuration backups, and resource-efficient AI routing to prevent system lag.

    While it excels at deployment and alert triage, the skill does not currently support active response actions such as automated IP blocking or process termination.

    No. Everything runs locally. Docker pulls the Wazuh images once during the initial deployment, then the skill operates offline. Ollama and Laya are also local.

    Windows 10/11, PowerShell 5.1+, Python 3.10+, Docker Desktop with WSL2 backend. About 8 GB of free disk space for Wazuh containers. 8 GB of RAM recommended if you also run Ollama.

    No. This skill is Windows-specific (PowerShell scripts, Windows service management for the Wazuh agent, ossec.conf at C:\Program Files (x86)\ossec-agent\)

    No. This is a deliberate design choice. The skill triages and summarizes alerts, then recommends actions. It never takes an active remediation step (IP block, process kill) without human approval.

    New in Security