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/foundry-skills --skill app-upgradesgit clone --depth 1 https://github.com/CrowdStrike/foundry-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/foundry-skills/app-upgrades)<a href="https://agentmods.dev/skills/crowdstrike/foundry-skills/app-upgrades"><img src="https://agentmods.dev/badge/skills/crowdstrike/foundry-skills/app-upgrades/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/foundry-skills/app-upgrades"><img src="https://agentmods.dev/badge/skills/crowdstrike/foundry-skills/app-upgrades.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.00123 | $0.01592 |
| Opus 5.5 | $0.00049 | $0.00637 |
| Sonnet 5.5 | $0.00025 | $0.00318 |
| Haiku 4.5 | $0.00012 | $0.00159 |
Grade A, and why
app-upgrades 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrading Template-Installed Apps
A Falcon Foundry template installs an app into a CID once. Nothing updates it when the template changes, and deploying the new template as-is creates a second app, because template manifests ship without IDs. This skill copies the installed app's IDs into the new version so foundry apps deploy updates the app the customer already has.
The template is the source of truth. The app keeps its current name. Changes the customer made after installing are overwritten; artifacts only the customer added are removed. Stop and confirm before anything is removed.
Inputs: the app ID, and optionally the new version as a .tar.gz/.tgz or .zip archive, an unpacked directory, or owner/repo[@ref]. With no version given, the skill finds the template by the app's name and uses its GitHub repo's default branch.
The script is scripts/upgrade_manifest.py in this skill's directory. It needs pyyaml, and crowdstrike-falconpy for find-template. Run it from a virtual environment outside the app directory.
Procedure
Use a new scratch directory per upgrade ($WORK below). Never sync or extract into the user's working copy.
-
Confirm the target.
foundry profile list --no-promptshows the active profile; the app must belong to its CID.foundry apps listmust show the app ID. If not, ask which profile tofoundry profile activate. -
Sync the deployed app.
list-deploymentsonly runs next to amanifest.ymlwith anapp_idand aname, even with--app-id, and an app installed from the console has no local directory. Give it a stub, take the newest version whose state is Successful, and sync that into scratch (syncruns from anywhere):mkdir -p "$WORK/stub" && printf 'app_id: %s\nname: stub\n' <app-id> > "$WORK/stub/manifest.yml" (cd "$WORK/stub" && foundry apps list-deployments --app-id <app-id>) foundry apps sync --app-id <app-id> --deployment-version <version> -d "$WORK/deployed" --replace-all --no-git --no-promptNo successful deployments means there's nothing to upgrade from; tell the user.
What ships with it
2 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.
- today Changed e2ae2a9a2003
- yesterday First seen · 77 lines · 123 tokens per session scan A e3a5cf388a0e
app-upgrades is a skill published in the GitHub repository CrowdStrike/foundry-skills (35 stars, last pushed today), licensed MIT. It adds 123 tokens to every session and 1,592 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-10-27.
Other skills, from other repositories
foundry-redirect
TRIGGER when the user asks to "build a Foundry app", "create a Foundry app", mentions manifest.yml, or needs a UI page/extension, serverless function, collection, or a custom API integration from a third-party API (Okta, ServiceNow, Jira, etc.) built. DO NOT TRIGGER for a standalone Fusion workflow that only wires…
flow-discover
Multi-AI research using available external providers (Double Diamond Discover phase).
flow-parallel
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates.
flow-define
Multi-AI requirements scoping using available external providers (Double Diamond Define phase). Priority triggers: octo define, octo scope, co-define, co-scope. DO NOT use for implementation, research, review/validation, or built-in commands.
skill-iterative-loop
Run tasks in a loop until goals are met — use for iterative refinement, polling, or convergence.
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.