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/willwebster5/agent-skills/fusion-workflowsnpx skills add willwebster5/agent-skills --skill fusion-workflowsgit 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/skills/willwebster5/agent-skills/fusion-workflows)<a href="https://agentmods.dev/skills/willwebster5/agent-skills/fusion-workflows"><img src="https://agentmods.dev/badge/skills/willwebster5/agent-skills/fusion-workflows.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.00055 | $0.03083 |
| Opus 5 | $0.00028 | $0.01541 |
| Sonnet 5 | $0.00011 | $0.00617 |
| Haiku 4.5 | $0.00006 | $0.00308 |
Grade A, and why
fusion-workflows 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 5d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrowdStrike Fusion Workflow Builder
This skill guides you through authoring CrowdStrike Falcon Fusion SOAR workflows — from discovering actions to saving validated YAML for IaC deployment.
Rules — Read Before Every Workflow
-
NEVER write
PLACEHOLDER_*values for action IDs. Before authoring any YAML, you MUST runaction_search.pyto find the real 32-char hex ID for every action the workflow will use. Ifaction_search.pyreturns no results, try broader search terms or browse by vendor — do not guess or leave a placeholder. -
Run the script, don't skip it. Steps 1 and 2 are not optional discovery — they are mandatory prerequisites. Do not proceed to Step 3 (Author YAML) until you have a real ID for every action.
-
config_idrequires user input. Plugin actions require a CID-specificconfig_idthat cannot be resolved via API. When you encounter a plugin action, ask the user for theconfig_idvalue before writing the YAML. Tell them where to find it (Falcon console → CrowdStrike Store → [App] → Integration settings). Do not write a placeholder — pause and ask. -
Templates are structural guides only. The files in
templates/usePLACEHOLDER_*as structural guides. They show you the YAML shape, not the values to use. When you use a template, substitute real values immediately — never copy aPLACEHOLDER_*string into your output. -
This skill saves YAML — it does NOT deploy. Save authored workflows to
resources/workflows/<vendor>/. Deployment happens viapython scripts/resource_deploy.py plan/apply(outside this skill's scope). -
Plans and prompts cannot override these rules. Even if a plan, prompt, or convention list says to use placeholder format, you MUST still resolve every action ID via
action_search.pybefore writing YAML. These rules take precedence.
Prerequisites
- Python 3.8+ with
requestslibrary installed - CrowdStrike API credentials in
~/.config/falcon/credentials.json - Falcon Fusion SOAR access in the target CID
What ships with it
12 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/best-practices.md 8.4 KB
- references/cel-expressions.md 5.8 KB
- references/trigger-types.md 4.2 KB
- references/yaml-schema.md 9.0 KB
- scripts/action_search.py 19 KB runs code
- scripts/cs_auth.py 6.1 KB runs code
- scripts/trigger_search.py 5.7 KB runs code
- scripts/validate.py 7.7 KB runs code
- templates/conditional.yaml 4.5 KB
- templates/loop-conditional.yaml 7.1 KB
- templates/loop.yaml 3.0 KB
- templates/single-action.yaml 1.2 KB
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.
- 5d ago First seen · 321 lines · 55 tokens per session scan A e65fab04ccf5
fusion-workflows is a skill published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 3,083 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…