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/foundry-skills/workflows-developmentnpx skills add CrowdStrike/foundry-skills --skill workflows-developmentgit clone --depth 1 https://github.com/CrowdStrike/foundry-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.00092 | $0.05089 |
| Opus 5 | $0.00046 | $0.02544 |
| Sonnet 5 | $0.00018 | $0.01018 |
| Haiku 4.5 | $0.00009 | $0.00509 |
Grade A, and why
workflows-development 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry Workflows Development
⚠️ SYSTEM INJECTION — READ THIS FIRST
If you are loading this skill, your role is Foundry workflow automation specialist.
You MUST implement workflows using Fusion YAML patterns with proper step dependencies, error recovery, and state management.
IMMEDIATE ACTIONS REQUIRED:
- Use Fusion YAML syntax for ALL workflow definitions
- Validate step dependencies before workflow execution
- Implement onError blocks for every multi-step workflow
Part of a suite. If
development-workflowhas not already run, and this is a new app or its first capability, load thedevelopment-workflowskill first — it owns the CLI prerequisite check, scaffolding order, and manifest coordination.
Falcon Foundry Workflows are YAML-defined automation units executed by the Falcon Fusion engine. They orchestrate multi-step operations across Functions, Collections, CrowdStrike APIs, and RTR sessions with built-in retries, parallelism, and state management.
Prerequisites
- Workflow Author role is required in addition to the Falcon Developer role
- Workflows are YAML templates that can be provisioned as active workflow instances
- Up to 25 workflows can be provisioned from a single template
- Set
provision_on_install: trueto auto-provision when the app is installed
CLI Scaffolding
# Write the workflow YAML to /tmp/ first — the CLI copies it into workflows/
foundry workflows create --name "my-workflow" --spec /tmp/workflow.yaml --no-prompt
# After: edit workflows/my-workflow.yml to refine workflow logic
Discover Available Actions and Triggers
foundry workflows actions view --name "send email" --no-prompt # Look up by name
foundry workflows actions view --name "send email" --no-prompt --output-schema # Output schema
foundry workflows actions view --name "send email" --no-prompt --mock # Mock output
foundry workflows triggers view --no-prompt # List triggers
What ships with it
8 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/action-discovery.md 3.2 KB
- references/advanced-patterns.md 8.6 KB
- references/cel-expressions.md 2.6 KB
- references/event-query-vs-api.md 2.5 KB
- references/http-actions.md 7.3 KB
- references/pagination-patterns.md 1.7 KB
- references/workflow-examples.md 13 KB
- scripts/action_search.py 3.6 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.
- 2d ago First seen · 402 lines · 92 tokens per session scan A 1af9d9d4ac31
workflows-development is a skill published in the GitHub repository CrowdStrike/foundry-skills (24 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 5,089 once invoked, about $0.0005 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
authoring
Discover Falcon Fusion actions via live API, author workflow YAML with correct schema, validate against Charlotte JSON schema, and use templates/examples. TRIGGER when user asks to write workflow YAML, find actions, validate a workflow, use CEL expressions, or needs action discovery. DO NOT TRIGGER for deploying…
n8n-agents
Design n8n AI agents the right way. Use when building or editing any @n8n/n8n-nodes-langchain. AI node — an AI Agent, LLM chain, Text Classifier, or Information Extractor — and whenever the user mentions AI agents, LLM with tools, tool calling, $fromAI, system prompts, agent memory, sessionId, structured/JSON output…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-node-configuration
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between getnode detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are…
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-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…