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 TIBCOSoftware/flogo-enterprise-hub --skill flogo-deploygit clone --depth 1 https://github.com/TIBCOSoftware/flogo-enterprise-hubWrote 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/tibcosoftware/flogo-enterprise-hub/flogo-deploy)<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.
<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>- NVIDIA SkillSpector pass
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.00034 | $0.01015 |
| Opus 5 | $0.00017 | $0.00508 |
| Sonnet 5 | $0.00007 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
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.
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
.flogofile (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 platformfullnameOverride— 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.
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.
- 12d ago First seen · 92 lines · 34 tokens per session scan A bb7773690648
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.
Other skills, from other repositories
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
agent-resource-allocator
Agent skill for resource-allocator - invoke with $agent-resource-allocator.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.