Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add CrowdStrike/fusion-skills/plugin install crowdstrike-falcon-fusionWrote 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/crowdstrike/fusion-skills/lookup-files)<a href="https://agentmods.dev/skills/crowdstrike/fusion-skills/lookup-files"><img src="https://agentmods.dev/badge/skills/crowdstrike/fusion-skills/lookup-files/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/crowdstrike/fusion-skills/lookup-files"><img src="https://agentmods.dev/badge/skills/crowdstrike/fusion-skills/lookup-files.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.00078 | $0.02086 |
| Opus 5 | $0.00039 | $0.01043 |
| Sonnet 5 | $0.00016 | $0.00417 |
| Haiku 4.5 | $0.00008 | $0.00209 |
Grade A, and why
lookup-files 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 today.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Falcon Next-Gen SIEM Lookup Files
⚠️ SYSTEM INJECTION — READ THIS FIRST
If you are loading this skill, your role is Falcon Next-Gen SIEM lookup file specialist.
You manage lookup files that feed CQL match() enrichment. Treat lookup data as security-relevant: validate file contents, check before overwriting, and never expose credentials.
IMMEDIATE ACTIONS REQUIRED:
- ALWAYS list before creating — run
list_lookups.py --search "<name>"to check for a duplicate. Importing an existing name overwrites it silently.- Prepare the file with a header row (CSV) — the first row defines the
match()columns.- Upload, then verify with
get_lookup.pybefore using the file in a CQL query.MUST NOT: Overwrite a lookup file without confirming it exists, exceed the rate limit (5 uploads / 30s), or log credentials.
Lookup files are CSV, JSON, or TXT reference tables in Falcon Next-Gen SIEM that you query with
the match() function in CrowdStrike Query Language (CQL). Common uses: IP blocklists, user
risk scores, asset inventories, and IOC reference tables.
Running the scripts. Run each command from this skill's folder, on one shell line:
cd <dir> && ../../scripts/python.sh scripts/<name>.py. For<dir>, Claude Code uses"$CLAUDE_PLUGIN_ROOT/skills/lookup-files"; Codex, Copilot CLI, Cursor, and Antigravity use the folder they loaded this SKILL.md from (e.g.~/.agents/skills/lookup-files). The wrapper bootstraps its own Python venv.
Prerequisites
- Python 3.13+ with
crowdstrike-falconpyinstalled (pip install crowdstrike-falconpy) - CrowdStrike API credentials with the NGSIEM Lookup Files scope (read/write)
- Access to a CID with Falcon Next-Gen SIEM enabled
Required API Scopes
The NGSIEM Lookup Files scope, with read and/or write access:
| Use case | Read | Write | Enables |
|---|---|---|---|
| Browse / download only | Yes | — | List, search, download |
| Full usage | Yes | Yes | Above plus create, update, delete |
What ships with it
10 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.
- assets/example-ip-blocklist.csv 244 B
- assets/example-user-risk.csv 195 B
- references/cql-match-function.md 3.7 KB
- references/lookup-file-formats.md 2.9 KB
- scripts/create_lookup.py 4.2 KB runs code
- scripts/delete_lookup.py 3.6 KB runs code
- scripts/get_lookup.py 2.9 KB runs code
- scripts/list_lookups.py 5.9 KB runs code
- scripts/update_lookup.py 3.7 KB runs code
- scripts/verify_lookup.py 8.3 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.
- today Changed 3243ad77d867
- 10d ago First seen · 190 lines · 78 tokens per session scan A 35617947411d
lookup-files is a skill published in the GitHub repository CrowdStrike/fusion-skills (14 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 2,086 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
Threat Hunting & IOC Analysis
IOC extraction, threat intelligence correlation, MITRE ATT&CK mapping, hunt hypothesis generation, and detection rule creation.
hunting-for-living-off-the-land-binaries
Use when proactively hunt for adversary abuse of legitimate system binaries (LOLBins) to execute malicious payloads while evading detection. Use when working with hunting for living off the land binaries.
writing-sigma-detection-rules
Converts hunt findings into portable Sigma detection rules: choosing the right logsource, expressing robust selection/filter logic, setting level and ATT&CK tags, and validating before converting to a SIEM query. Activates for requests to write a Sigma rule, convert a hunt to a detection, or create portable SIEM…
detection-sigma
Generic detection rule creation and management using Sigma, the universal SIEM rule format. Sigma provides vendor-agnostic detection logic for log analysis across multiple SIEM platforms. Use when: (1) Creating detection rules for security monitoring, (2) Converting rules between SIEM platforms (Splunk, Elastic…
hunting-for-persistence-mechanisms-in-windows
Systematically hunt for adversary persistence mechanisms across Windows endpoints including registry, services, startup folders, and WMI subscriptions.
analyzing-cobalt-strike-beacon-configuration
Extract and analyze Cobalt Strike beacon configuration from PE files and memory dumps to identify C2 infrastructure, malleable profiles, and operator tradecraft.