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 skills add CrowdStrike/fusion-skills --skill foundry-redirectgit clone --depth 1 https://github.com/CrowdStrike/fusion-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/crowdstrike/fusion-skills/foundry-redirect)<a href="https://agentmods.dev/skills/crowdstrike/fusion-skills/foundry-redirect"><img src="https://agentmods.dev/badge/skills/crowdstrike/fusion-skills/foundry-redirect/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/foundry-redirect"><img src="https://agentmods.dev/badge/skills/crowdstrike/fusion-skills/foundry-redirect.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.00126 | $0.00727 |
| Opus 5.5 | $0.00050 | $0.00291 |
| Sonnet 5.5 | $0.00025 | $0.00145 |
| Haiku 4.5 | $0.00013 | $0.00073 |
Grade A, and why
foundry-redirect 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 23d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Falcon Foundry Redirect
If this skill triggered, the request is a Falcon Foundry app, not a standalone
Falcon Fusion workflow. It belongs to the sibling Falcon Foundry plugin — the
fusion-skills plugin builds Fusion workflows only.
Why this skill exists: the workflows orchestrator declines Foundry-app requests too,
but its description matches Fusion workflow language, so a "build a Foundry app"
prompt never loads it. On Claude Code, Codex, Copilot CLI, and Cursor a hook covers that gap. On
assistants that do not load plugin hooks, this skill's description matches Foundry-app
language directly and makes the redirect reachable.
What to do
Do NOT author workflow YAML. Do NOT scaffold an app yourself. Respond with all three:
- State plainly that this request needs a Falcon Foundry app, not a standalone Fusion workflow.
- Name the plugin:
crowdstrike-falcon-foundry. - How to install it:
/plugin install crowdstrike-falcon-foundryin Claude Code,/pluginsin Codex,copilot plugin install CrowdStrike/foundry-skillsin Copilot CLI,/add-plugin crowdstrike-falcon-foundryin Cursor, or clone https://github.com/CrowdStrike/foundry-skills.
When both plugins are installed
If crowdstrike-falcon-foundry is present, its own development-workflow skill matches
Foundry-app requests directly and handles them — a stronger match than this one, so the
agent picks it and this redirect never fires. That is correct: this skill is the safety
net for when the Foundry plugin is absent, not a competitor with it when present.
Foundry app vs. standalone workflow
| Signal in the request | Route |
|---|---|
"Foundry app", manifest.yml, a UI page/extension, serverless function, collection, or custom third-party API integration |
Here — redirect to foundry-skills |
| A trigger plus existing Fusion actions only (no UI, function, collection, or custom integration) | workflows — handle it as a standalone workflow |
| "a workflow inside a Foundry app" | Here — the app owns the workflow; Foundry scaffolds it |
| Fetch/summarize a population of alerts/detections the workflow doesn't already hold | workflows — a standalone CrowdStrike HTTP Request handles this without an app |
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.
- 23d ago Changed · -1 tokens per session 4b43b37ece0a
- 1mo ago Changed 396ecf2817de
- 1mo ago First seen · 56 lines · 127 tokens per session scan A 290f4763d84e
foundry-redirect is a skill published in the GitHub repository CrowdStrike/fusion-skills (27 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 727 once invoked, about $0.0005 per session on Opus 5.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
fusion-redirect
TRIGGER when user asks for a "standalone Falcon Fusion workflow" that needs NO Foundry app — just a trigger plus actions that already exist in their CID, with no UI, function, collection, or custom API integration to build. DO NOT TRIGGER when the request needs anything built (a custom action, a UI page, a function, a…
api-integrations
Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs foundry api-integrations create. Also trigger when user has an OpenAPI/Swagger spec and wants it…
development-workflow
Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment. TRIGGER when user asks to "create a Foundry app", "build a Foundry app", "plan a Foundry app", runs any foundry apps CLI command, or discusses Foundry app architecture. DO NOT TRIGGER when user is working on a specific…
e2e-testing
End-to-end testing for Falcon Foundry apps using Playwright and @crowdstrike/foundry-playwright. TRIGGER when user asks to "add e2e tests", "add playwright tests", "write end-to-end tests", "test my app", or mentions "e2e", "playwright", or "end-to-end" in the context of testing a Foundry app. DO NOT TRIGGER during…
functions-falcon-api
Call CrowdStrike Falcon platform APIs (detections, alerts, hosts, RTR) from within Foundry function handlers. TRIGGER when user asks to "call Falcon APIs from a function", "use FalconPy in a function", "use gofalcon in a function", or needs to integrate Falcon platform APIs within serverless function code. DO NOT…
ui-development
Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs foundry ui pages create or foundry ui run, or needs help with Vite…