flogo-deploy

flogo-deploy is a skill for Claude Code from TIBCOSoftware/flogo-enterprise-hub. It costs 34 tokens per session (1,015 once invoked), scanned A, original, Apache-2.0.

A deployment procedure for sending a TIBCO Flogo application to a TIBCO Platform dataplane. Flogo is a tool for building applications from workflows, and a dataplane is the target environment where the application runs.

In plain words
What is it for?
Use it to locate a .flogo application file, choose an available Flogo version, create a build, and deploy it to a named dataplane with an authenticated profile.
Why use it?
It turns the required lookup, build, and deployment steps into a repeatable process using the TIBCO command-line tool.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md.

Good fit Use it to locate a .flogo application file, choose an available Flogo version, create a build, and deploy it to a named dataplane with an authenticated profile.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy
Install

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.

Any agent
npx skills add TIBCOSoftware/flogo-enterprise-hub --skill flogo-deploy
Clone the repo
git clone --depth 1 https://github.com/TIBCOSoftware/flogo-enterprise-hub

Made for: Claude Code.

Wrote 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.

agentmods badge for flogo-deploy

README.md
[![agentmods](https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy/github.svg)](https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy)
Your own site
<a href="https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy/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.

agentmods 80×15 button for flogo-deploy

Your own site · 80×15
<a href="https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogo-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,015 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01015
Opus 5 $0.00017 $0.00508
Sonnet 5 $0.00007 $0.00203
Haiku 4.5 $0.00003 $0.00102

Measured 12d ago against content hash bb7773690648, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

flogo-deploy 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 12d 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.

skills-library/.claude/skills/flogo-deploy/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy a Flogo Application to the TIBCO Platform

This skill deploys a .flogo application file to a TIBCO Platform dataplane using the tibcop CLI. Use the TIBCO Platform CLI profile configured for your environment (e.g. set in your project's CLAUDE.md as <YOUR_PROFILE>).

Required Inputs

  • Flogo app file: Path to the .flogo file (check the Flogo apps folder if not specified, e.g. ./Flogo_Apps/)
  • Dataplane name: The target dataplane to deploy to
  • Profile: The TIBCO Platform CLI profile to authenticate with

Deployment Steps

Follow these steps in order:

Step 1: Locate the Flogo app file

Find the .flogo file. If the user provides just an app name, look for it in the configured apps folder (e.g. ./Flogo_Apps/<appName>.flogo) first, then search the project.

Step 2: List available Flogo versions on the dataplane

tibcop flogo:list-flogo-versions --profile <YOUR_PROFILE> --dataplane-name <DATAPLANE_NAME> --json

Pick the available buildtypeTag from the response (e.g. 2.25.9-b300).

Step 3: Create a build

tibcop flogo:create-build --profile <YOUR_PROFILE> --dataplane-name <DATAPLANE_NAME> --flogo-version <FLOGO_VERSION> --json <PATH_TO_FLOGO_FILE>

This will return a buildId and status. Wait for status Success before proceeding.

Step 4: Generate values.yaml from the build

tibcop flogo:generate-values-from-build --profile <YOUR_PROFILE> --dataplane-name <DATAPLANE_NAME> --build-id <BUILD_ID> --output-dir <OUTPUT_DIR>

Use the same directory as the flogo file for the output. This generates a values.yaml with all the correct deployment configuration.

Step 5: Set the app name in values.yaml

If the user specified a custom app name, update both of these fields in values.yaml before deploying:

  • appConfig.originalAppName — the display name in the platform
  • fullnameOverride — the runtime name (Kubernetes release name)

If you skip fullnameOverride, the app will appear as the generic flogo-project in the runtime even though originalAppName is correct.

Read the full file on GitHub · 92 lines

Changes

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.

  1. 12d ago First seen · 92 lines · 34 tokens per session scan A bb7773690648

Subscribe to this mod's changes

flogo-deploy is a skill published in the GitHub repository TIBCOSoftware/flogo-enterprise-hub (14 stars, last pushed 4d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,015 once invoked, about $0.0002 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.