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/crowdsec-service-apinpx skills add crowdsecurity/crowdsec-skill --skill crowdsec-service-apigit clone --depth 1 https://github.com/crowdsecurity/crowdsec-skillWrote 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/crowdsecurity/crowdsec-skill/crowdsec-service-api)<a href="https://agentmods.dev/skills/crowdsecurity/crowdsec-skill/crowdsec-service-api"><img src="https://agentmods.dev/badge/skills/crowdsecurity/crowdsec-skill/crowdsec-service-api.svg" alt="Measured on agentmods" 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 | $0.00135 | $0.02012 |
| Opus 5 | $0.00068 | $0.01006 |
| Sonnet 5 | $0.00027 | $0.00402 |
| Haiku 4.5 | $0.00014 | $0.00201 |
Grade C, and why
crowdsec-service-api scanned grade C with 3 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| Add IPs to a blocklist *(mutating — confirm)* | `curl -s -H "x-api-key: $KEY" -H 'Content-Type: application/json' -X POST "$B/blocklists/$ID/ips" -d '{"ips":["1.2.3.4"]}'` | Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
[ -n "$KEY" ] || echo "No key: export CROWDSEC_SAPI_KEY or store it in ~/.config/crowdsec/sapi_key (chmod 0600)" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "x-api-key: $KEY" https://admin.api.crowdsec.net/v1/info How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrowdSec Service API (SAPI) — cloud blocklist / allowlist / integration automation
SAPI is the premium REST API behind the CrowdSec Console. It manages
cloud-side objects (private blocklists, allowlists, decisions, firewall integrations)
that then push down to enrolled engines and bouncers. It is not the local
engine API — there is no cscli here, only HTTPS.
- Base URL:
https://admin.api.crowdsec.net/v1 - Auth:
x-api-key: <key>header on every call. (One exception: the integration content endpoint uses HTTP Basic with credentials minted at integration creation — see references/integrations.md.) - Interactive API docs: https://admin.api.crowdsec.net/v1/docs · spec https://admin.api.crowdsec.net/v1/openapi.json
Boundary — this skill vs the crowdsec skill
| You want to… | Use |
|---|---|
| Create/manage a private blocklist in the cloud, push IPs to it via API | this skill |
| Wire a firewall/appliance (Palo Alto, Fortinet…) to a cloud integration | this skill |
| Manage cloud allowlists, subscribe engines/tags/orgs to lists | this skill |
| Create/manage org-level decisions (targeted or ad-hoc bans, non-IP scopes, per tag/entity) | this skill |
| Pull remediation ROI metrics | this skill |
Install / run / debug the local engine, cscli, bouncers, WAF |
the crowdsec skill |
Enroll an engine into the Console (cscli console enroll) |
the crowdsec skill → references/install/console.md |
| Configure a local allowlist/whitelist on one engine | the crowdsec skill → references/configure/allowlists.md |
Cloud allowlists/blocklists here only take effect on an engine once that engine
is enrolled and subscribed to the list. The enrollment half lives in the
crowdsec skill.
Operating contract
Every call here hits production and can change what subscribed engines enforce.
1 — Resolve the key. Never echo it, never write it anywhere but the file below:
KEY="${CROWDSEC_SAPI_KEY:-$(cat ~/.config/crowdsec/sapi_key 2>/dev/null)}"
[ -n "$KEY" ] || echo "No key: export CROWDSEC_SAPI_KEY or store it in ~/.config/crowdsec/sapi_key (chmod 0600)"
What ships with it
6 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.
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.
- 4d ago First seen · 126 lines · 135 tokens per session scan C ff9c3031c62f
crowdsec-service-api is a skill published in the GitHub repository crowdsecurity/crowdsec-skill (23 stars, last pushed 2d ago), licensed MIT. It adds 135 tokens to every session and 2,012 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 3 findings (sends data to an external url, 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…