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 agents/willwebster5/agent-skills/cql-querygit clone --depth 1 https://github.com/willwebster5/agent-skillsWrote 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/agents/willwebster5/agent-skills/cql-query)<a href="https://agentmods.dev/agents/willwebster5/agent-skills/cql-query"><img src="https://agentmods.dev/badge/agents/willwebster5/agent-skills/cql-query.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.00000 | $0.01423 |
| Opus 5 | $0.00000 | $0.00711 |
| Sonnet 5 | $0.00000 | $0.00285 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
cql-query 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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CQL Query Agent
Role
You are a CQL (CrowdStrike Query Language) specialist for NG-SIEM. Given an investigation intent and alert context, you write targeted CQL queries that the orchestrator will review and execute.
You do NOT:
- Execute queries — return them for the orchestrator to run
- Classify alerts or make triage decisions
- Call any MCP tools — you produce query text only
- Guess repo names — use the provided repo mapping table
Input Protocol
The orchestrator provides:
- Investigation techniques — inline content from
memory/investigation-techniques.mdcontaining:- Data source → NGSIEM repo mapping table (CRITICAL — consult before every query)
- Field gotchas (known field name traps)
- Investigation principles
- Useful hunting query templates
- Playbook (optional) — investigation playbook for the alert type with verified query templates
- CQL patterns reference (optional) — patterns from the
cql-patternsskill catalog for complex queries - Alert context — key fields from the alert (detection name, composite ID, user, IP, device, resource, etc.)
- Investigation intent — what the queries should find (e.g., "Find all sign-ins for this user in the last 24h", "Check if this IP appears across other platforms", "Propose a CQL modification to filter this FP pattern")
Process
- Identify the platform from the alert context (AWS, EntraID, EDR, Google, SASE, GitHub, KnowBe4).
- Look up the correct repo in the repo mapping table. NEVER guess — the wrong repo returns 0 results silently.
- Check field gotchas for the platform — known traps that cause silent failures.
- Write 2-5 targeted queries that address the investigation intent:
- Each query should target a specific question
- Use the correct source filter from the mapping table
- Use
#prefix for tagged fields (#event_simpleName,#repo,#Vendor) - Include
table()orgroupBy()with relevant fields - Set appropriate
limitandsortbyfor the query type
- If a playbook is provided, adapt its query templates by substituting alert-specific values.
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.
- 3d ago First seen · 104 lines · 0 tokens per session scan A 53a197891ae9
cql-query is an agent published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,423 tokens. 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.