Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add CarbeneAI/Forge --skill wazuhdashboardgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/carbeneai/forge/wazuhdashboard)<a href="https://agentmods.dev/skills/carbeneai/forge/wazuhdashboard"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/wazuhdashboard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/carbeneai/forge/wazuhdashboard"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/wazuhdashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00048 | $0.01127 |
| Opus 5 | $0.00024 | $0.00563 |
| Sonnet 5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
WazuhDashboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WazuhDashboard
Real-time security monitoring dashboard for Wazuh SIEM alerts with integrated PAI chat for contextual analysis.
Architecture
Wazuh (10.0.0.60) → n8n webhook → JSONL file → Dashboard Server (WebSocket) → Vue Client
↓
PAI API (localhost:3001)
Features
- Real-time Alert Feed: Live streaming of Wazuh security alerts via WebSocket
- Severity Color-coding: Visual priority indicators (Critical, High, Medium, Low)
- Split-screen Layout: 60% alerts feed, 40% PAI chat panel
- Alert Filtering: Filter by severity, agent, rule group
- PAI Chat Integration: Context-aware security analysis
- Quick Actions: "Analyze", "Remediation", "Related?" buttons
Ports
| Component | Port | URL |
|---|---|---|
| Server (API/WebSocket) | 4001 | http://localhost:4001 |
| Client (Vue/Vite) | 5173 | http://localhost:5173 |
| Production | 443 | https://wazuh-dashboard.home.yourdomain.com |
Severity Levels
| Level | Range | Color | Hex |
|---|---|---|---|
| Critical | 12+ | Red | #f7768e |
| High | 7-11 | Amber | #e0af68 |
| Medium | 3-6 | Purple | #bb9af7 |
| Low | 0-2 | Green | #9ece6a |
Management
# Start dashboard
~/.claude/skills/WazuhDashboard/manage.sh start
# Stop dashboard
~/.claude/skills/WazuhDashboard/manage.sh stop
# Restart
~/.claude/skills/WazuhDashboard/manage.sh restart
# Check status
~/.claude/skills/WazuhDashboard/manage.sh status
Configuration
Environment Variables
Add to ~/.claude/.env:
WAZUH_PAI_API_KEY=<your-claude-api-key>
WAZUH_ALERTS_PATH=/path/to/your/wazuh-alerts/alerts.jsonl
n8n Webhook
Configure n8n workflow to receive Wazuh alerts and append to JSONL file:
- Webhook URL:
https://n8n.home.yourdomain.com/webhook/wazuh-alerts - Output: Append JSON to
$WAZUH_ALERTS_PATH
Wazuh Integration
Add to /var/ossec/etc/ossec.conf on Wazuh manager (configure your Wazuh IP):
What ships with it
39 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .gitignore 227 B
- apps/client/bun.lock 38 KB
- apps/client/index.html 714 B
- apps/client/package.json 579 B
- apps/client/postcss.config.js 80 B runs code
- apps/client/public/shield.svg 270 B
- apps/client/src/App.vue 9.0 KB
- apps/client/src/components/AlertFeed.vue 3.7 KB
- apps/client/src/components/AlertRow.vue 7.2 KB
- apps/client/src/components/AlertStats.vue 4.8 KB
- apps/client/src/components/ChatPanel.vue 6.5 KB
- apps/client/src/components/FilterPanel.vue 5.8 KB
- apps/client/src/components/Toast.vue 1.2 KB
- apps/client/src/composables/usePAIChat.ts 3.0 KB runs code
- apps/client/src/composables/useToast.ts 683 B runs code
- apps/client/src/composables/useWebSocket.ts 3.7 KB runs code
- apps/client/src/main.ts 117 B runs code
- apps/client/src/styles/main.css 2.0 KB
- apps/client/src/types.ts 2.0 KB runs code
- apps/client/src/vite-env.d.ts 191 B runs code
- apps/client/tailwind.config.js 1.3 KB runs code
- apps/client/tsconfig.json 601 B
- apps/client/tsconfig.node.json 233 B
- apps/client/tsconfig.node.tsbuildinfo 35 KB
- apps/client/tsconfig.tsbuildinfo 336 B
- apps/client/vite.config.d.ts 76 B runs code
- apps/client/vite.config.js 354 B runs code
- apps/client/vite.config.ts 363 B runs code
- apps/server/bun.lock 1.2 KB
- apps/server/package.json 357 B
- apps/server/src/alert-ingest.ts 11 KB runs code
- apps/server/src/index.ts 9.8 KB runs code
- apps/server/src/pai-client.ts 15 KB runs code
- apps/server/src/suricata-suppression.ts 9.3 KB runs code
- apps/server/src/types.ts 3.5 KB runs code
- apps/server/tsconfig.json 260 B
- manage.sh 2.4 KB runs code
- wazuh-dashboard.service 669 B
- workflows/Deploy.md 6.9 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 153 lines · 48 tokens per session scan A 85651293f3ff
WazuhDashboard is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,127 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
panguard
AI agent security platform — audit skills, scan for threats, and run 24/7 protection with 9,700+ detection rules.
detecting-aws-credential-exposure-with-trufflehog
Detecting exposed AWS credentials in source code repositories, CI/CD pipelines, and configuration files using TruffleHog, git-secrets, and AWS-native detection mechanisms to prevent credential theft and unauthorized account access.