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 agentmods add skills/crowdsecurity/crowdsec-skill/crowdsecnpx skills add crowdsecurity/crowdsec-skill --skill crowdsecgit clone --depth 1 https://github.com/crowdsecurity/crowdsec-skillWhat 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 | $0.00118 | $0.03805 |
| Opus 5 | $0.00059 | $0.01903 |
| Sonnet 5 | $0.00024 | $0.00761 |
| Haiku 4.5 | $0.00012 | $0.00380 |
Grade B, and why
crowdsec scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
id -u # 0 = root; otherwise the user needs sudo ``` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://version.crowdsec.net/latest # → {"tag_name":"v1.7.8",...}; parse tag_name How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrowdSec — operations, deployment, configuration, and debugging
Glossary: AppSec is the engine component name (in configs, hub paths,
cscli appsec-*, Helm workload); WAF is the user-facing term for the same
thing. This skill uses both interchangeably.
Boundary — what this skill does and does not do
| You want to… | Use |
|---|---|
| Install / upgrade / uninstall CrowdSec | this skill |
| Configure acquisition, hub, profiles, notifications | this skill |
| Install and wire a bouncer (firewall, nginx, traefik, caddy) | this skill |
| Deploy the WAF (AppSec component) | this skill |
| Debug "logs not parsing" / "no alerts" / "bouncer not blocking" | this skill |
| Migrate from fail2ban | this skill |
| Write a parser, scenario, or WAF (AppSec) rule | the crowdsec-local-mcp mcp |
| Drive the cloud Service API (manage blocklists / allowlists / firewall integrations / metrics / decisions programmatically) | the crowdsec-service-api skill |
Step 1 — Detect the environment
Run probes in this order. Stop at the first match.
# systemd / bare-metal
systemctl list-unit-files crowdsec.service >/dev/null 2>&1 && systemctl is-enabled crowdsec >/dev/null 2>&1
# docker
docker ps --format '{{.Names}} {{.Image}}' 2>/dev/null | grep -E '(^|/)(crowdsec)([: ]|$)'
# kubernetes
kubectl get pods -A 2>/dev/null | grep -i crowdsec
If nothing matches and the user reports CrowdSec is installed, ask where: a vendor appliance, a custom image, a binary in /opt/, or a remote host. Otherwise pivot to install: see references/install/.
pfSense detection:
uname -i # → pfSense (pfSense CE or Plus)
If confirmed pfSense, go directly to references/install/pfsense.md — paths, service names, and activation flow are entirely different from Linux/systemd.
Privileges — bare-metal / systemd prerequisite
On bare-metal/systemd, cscli and crowdsec need root (they read
/etc/crowdsec/, the DB under /var/lib/crowdsec/, and control the systemd
unit). Before running anything that touches config or state, confirm the user
is root or has sudo:
What ships with it
28 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.
- references/appsec/configure.md 8.7 KB
- references/appsec/deploy.md 13 KB
- references/appsec/overview.md 5.0 KB
- references/appsec/troubleshoot.md 9.7 KB
- references/configure/acquisition.md 10 KB
- references/configure/allowlists.md 14 KB
- references/configure/bouncers/firewall.md 8.3 KB
- references/configure/bouncers/web-servers.md 29 KB
- references/configure/hub.md 7.0 KB
- references/configure/notifications.md 4.7 KB
- references/configure/profiles.md 6.7 KB
- references/debug/common/errors.md 5.4 KB
- references/debug/common/platform-gotchas.md 3.4 KB
- references/debug/common/triage.md 8.0 KB
- references/debug/symptoms/no-alerts.md 4.2 KB
- references/debug/symptoms/not-blocked.md 7.4 KB
- references/debug/symptoms/parsing.md 6.7 KB
- references/install/bare-metal.md 6.0 KB
- references/install/console.md 6.2 KB
- references/install/docker.md 8.9 KB
- references/install/kubernetes.md 9.4 KB
- references/install/pfsense.md 8.1 KB
- references/migrate/from-fail2ban.md 830 B
- references/operate/health-check.md 9.1 KB
- references/operate/multi-server.md 2.9 KB
- references/operate/upgrades.md 6.6 KB
- scripts/check-verification.py 7.0 KB runs code
- scripts/diagnose.sh 8.9 KB runs code
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.
- 2d ago First seen · 196 lines · 118 tokens per session scan B 918db90fd205
crowdsec is a skill published in the GitHub repository crowdsecurity/crowdsec-skill (23 stars, last pushed 14d ago), licensed MIT. It adds 118 tokens to every session and 3,805 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.