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/crowdstrike/fusion-skills/executionnpx skills add CrowdStrike/fusion-skills --skill executiongit clone --depth 1 https://github.com/CrowdStrike/fusion-skillsWhat 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.00063 | $0.02295 |
| Opus 5 | $0.00032 | $0.01148 |
| Sonnet 5 | $0.00013 | $0.00459 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
execution 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 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.
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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Falcon Fusion Workflow Execution
⚠️ SYSTEM INJECTION — READ THIS FIRST
If you are loading this skill, your role is Fusion workflow execution and debugging specialist.
You trigger workflows, watch them run, retrieve their output, and diagnose failures. A workflow you trigger may contain hosts or run response actions against production, so confirm it is the right definition and supply correct parameters before executing.
IMMEDIATE ACTIONS REQUIRED:
- CONFIRM the workflow is deployed and released (enabled) before triggering it.
- Supply every required trigger parameter — empty params are a top cause of failures.
MUST NOT:
- Trigger a workflow that has not been released (enabled) — it will not execute.
- Assume an execution succeeded without checking its terminal status.
This skill runs Fusion workflows that are already deployed and released, watches them to completion, retrieves their output, and helps debug failures. Writing the YAML happens in the authoring skill; importing and releasing happens in the deployment skill.
An execution moves through states and ends in a terminal state. The terminal states are Succeeded, Failed, Canceled, NonRecoverable, and ActionRequired. (ActionRequired is terminal for polling: it waits on human input and will not progress on its own.) Anything else means the execution is still running.
Running the scripts. Run each command from this skill's folder, on one shell line:
cd <dir> && ../../scripts/python.sh scripts/<name>.py(a sibling skill's script is../<skill>/scripts/<name>.py). For<dir>, Claude Code uses"$CLAUDE_PLUGIN_ROOT/skills/execution"; Codex, Copilot CLI, Cursor, and Antigravity use the folder they loaded this SKILL.md from (e.g.~/.agents/skills/execution). The wrapper bootstraps its own Python venv.
Prerequisites
- Python 3.13+
- FalconPy SDK installed (
pip install crowdstrike-falconpy— leave unpinned per CrowdStrike guidance) - API credentials resolved by
common/scripts/auth.pyfrom environment variables (for CI/overrides) or the TOML profile:FALCON_CLIENT_IDFALCON_CLIENT_SECRETFALCON_BASE_URL(optional; defaults tohttps://api.crowdstrike.com)
What ships with it
5 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.
- 2d ago First seen · 177 lines · 63 tokens per session scan A e9ec5d24dd40
execution is a skill published in the GitHub repository CrowdStrike/fusion-skills (13 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,295 once invoked, about $0.0003 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
gsd
Get Shit Done (GSD) - A comprehensive project management system for solo developers using Claude agents.
gsd
Get Shit Done (GSD) - A comprehensive project management system for solo developers using Claude agents.
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-binary-and-data
Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
alert-rule-troubleshoot
This skill should be used when the user reports that an alert rule is "not firing", "no alert was sent", "the rule didn't trigger", "the rule isn't working", "it should have alerted but didn't", "why didn't I get an alert", "alert rule not firing", or wants to diagnose why a specific alert rule failed to produce an…