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 gensecaihq/Wazuh-Autopilot --skill wazuh-sca-hardeninggit clone --depth 1 https://github.com/gensecaihq/Wazuh-AutopilotWrote 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/gensecaihq/wazuh-autopilot/wazuh-sca-hardening)<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/wazuh-sca-hardening"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-sca-hardening/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/gensecaihq/wazuh-autopilot/wazuh-sca-hardening"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-sca-hardening.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.00071 | $0.01264 |
| Opus 5.5 | $0.00028 | $0.00506 |
| Sonnet 5 | $0.00014 | $0.00253 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
wazuh-sca-hardening 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 yesterday.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wazuh SCA Hardening
Wazuh SCA runs policy files (mostly CIS Benchmarks: cis_ubuntu22-04, cis_win2022, cis_rhel9, …) on
each agent and reports each check as passed, failed or not applicable, plus an overall score.
SCA rules (stock ruleset, group sca)
| Rule | Level | Meaning |
|---|---|---|
| rule 19001 | 3 | SCA summary: policy score |
| rule 19002 | 4 | Score less than 90% |
| rule 19003 | 5 | Score less than 80% |
| rule 19004 | 7 | Score less than 50% |
| rule 19005 | 9 | Score less than 30% |
| rule 19007 | 7 | Check result failed (sca.check.result: failed) |
| rule 19008 | 3 | Check result passed |
| rule 19009 | 3 | Check result not applicable |
| rule 19010 | 3 | Status changed from failed to passed (remediated) |
| rule 19011 | 9 | Status changed from passed to failed (regression) |
| rule 19012 | 5 | Status changed from passed to not applicable |
A regression (rule 19011) is the most important SCA signal: something that was compliant stopped being compliant. It can mean drift, a bad change — or an attacker weakening a host (disabling auditing, enabling root SSH login). Treat regressions on servers as potential incidents, not just hygiene.
Key fields
sca.policy, sca.policy_id, sca.check.id, sca.check.title, sca.check.result,
sca.check.previous_result, sca.check.rationale, sca.check.remediation, sca.check.compliance.*
(CIS, PCI DSS, NIST 800-53, HIPAA, ISO mappings shipped in the policy), sca.score, sca.passed,
sca.failed.
Getting the data
- Current state:
get_sca_policy_checks agent_id="<id>"(optionallypolicy_id) — returns checks with result, rationale and remediation. - Changes over time:
get_wazuh_alerts rule_groups=["sca"] agent_id="<id>" timestamp_start="now-7d"; regressions only: filter therule_idparameter on rule 19011. - Fleet view: iterate agents from
get_wazuh_agents status="active"— keep it to the in-scope set (servers, internet-facing, crown jewels) to stay within budget.
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.
- yesterday First seen · 89 lines · 71 tokens per session scan A 9253446cfa41
wazuh-sca-hardening is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (57 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 1,264 once invoked, about $0.0003 per session on Opus 5.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-25.
Other skills, from other repositories
external-privacy-guard
A privacy rule set for conversations that include people other than the account owner. It checks who is participating and limits what personal or confidential information may be shared.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-topology-optimizer
Agent skill for topology-optimizer - invoke with $agent-topology-optimizer.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-repo-architect
Agent skill for repo-architect - invoke with $agent-repo-architect.