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 tibcopgit 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/tibcop)<a href="https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/tibcop"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/tibcop/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/tibcop"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/tibcop.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.01496 |
| Opus 5 | $0.00017 | $0.00748 |
| Sonnet 5 | $0.00007 | $0.00299 |
| Haiku 4.5 | $0.00003 | $0.00150 |
Grade A, and why
tibco-platform-cli 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 11d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The following tasks are available:
tibcop --help
TIBCO Platform CLI
USAGE
$ tibcop [COMMAND]
TOPICS
bw5ce TIBCO Platform Commands for Business Work 5 Container Edition (BW5)
bwce TIBCO Platform Commands for Business Work Container Edition (BWCE)
flogo TIBCO Platform Commands for Flogo
plugins Manage plugins of the TIBCO Platform CLI
thub TIBCO Platform Commands for the TIBCO Developer Hub
tplatform Commands for the TIBCO Platform
COMMANDS
add-profile Add profiles to your configuration
ap Add profiles to your configuration
autocomplete Display autocomplete installation instructions.
clean-all Remove all profiles, configurations, CLI plugins and cache data
di Display installation details
display-installation Display installation details
help Display help for tibcop.
init Initialize the CLI and create your default profile
initialize Initialize the CLI and create your default profile
list-profiles List all configured profiles
login Relogin for a profile
lp List all configured profiles
plugins List installed plugins.
refresh-token Refresh token for a profile
remove-profile Remove profiles from the configuration
rp Remove profiles from the configuration
rt Refresh token for a profile
sp Change the default profile
switch-profile Change the default profile
update-profile Update profile in the configuration
To get help on a specific topic, run
tibcop <topic> --help, for example:
tibcop flogo --help
TIBCO Platform Commands for Flogo
USAGE
$ tibcop flogo:COMMAND
COMMANDS
flogo:build-info Get detailed build info about FLOGO application build. The output contains the details like build OS,
arch, base version, build time, etc. for the provided build Id
flogo:capability-info Show FLOGO Capability info from the data plane
flogo:create-build Create a TIBCO FLOGO application build. The command expects application (.flogo or .json) file, flogo
base version and build tags as an input along with connector dependencies details
flogo:delete-app Delete FLOGO app from the data plane
flogo:delete-build Delete an application build. Please ensure the build to be deleted is not used by any application
flogo:delete-connector Delete connector from the dataplane. Please ensure the connector to be deleted is not used in any
application or build
flogo:delete-flogo-version Delete provisioned FLOGO version from the dataplane. Please ensure the FLOGO version to be deleted is not
used by any application or build
flogo:delete-supplement Delete connector supplement from the dataplane. Please ensure the supplement to be deleted is not used in
any application or build
flogo:deploy-app Deploy or upgrade a flogo application using build Id. The API lets you provide override app properties,
engine variables, resource limits for the pod, replicas or autoscaling configuration and network policy
configurations while deploying or upgrading the app. An appId in payload is mandatory only for upgrading
an existing application, otherwise it should be empty
flogo:deploy-app-release Deploy or upgrade a FLOGO application helm chart using values.yaml. An appId inside values.yaml is
mandatory for upgrading an existing application
flogo:export-build Export flogo app build from the data plane
flogo:generate-values-from-build Generate values.yaml from an app build
flogo:get-app-release-history Release history of an application deployment for an app Id. This is applicable only for FLOGO helm
managed applications
flogo:get-app-release-status Get FLOGO helm managed app release status from the data plane
flogo:get-app-release-values Get FLOGO helm managed app release values from the data plane
flogo:get-build-status Get FLOGO app build status from the data plane
flogo:import-build Import FLOGO app build on the data plane
flogo:list-app-endpoints List application endpoints for a FLOGO app. The API returns details about public/private endpoints and
ingress configuration for the public endpoints
flogo:list-app-instances Get list of application instances for provided app Id
flogo:list-builds List FLOGO app builds from the data plane
flogo:list-connectors List FLOGO connectors from the data plane
flogo:list-flogo-versions List FLOGO versions provisioned in the data plane
flogo:list-supplements List supplements from the data plane
flogo:provision-connector Provision FLOGO connector on the data plane
flogo:provision-flogo-version Provision FLOGO version on the data plane
flogo:rollback-app-release Rollback an application helm chart release for an app Id to the specified revision
flogo:scale-app Scale FLOGO app from the data plane
flogo:update-app Update FLOGO application configuration for FLOGO provisioner managed application. The application will
restart while applying the configuration
flogo:update-app-autoscaling Create, modify or remove autoscaling configuration for a FLOGO Provisioner managed application. You can
provide min/max replicas and CPU/memory thresholds for the HPA resource configuration
flogo:update-app-endpoint-visibility Make an application endpoint public or private for FLOGO provisioner managed apps. The API creates an
ingress resource with provided inputs - ingress class name, FQDN, path prefix, etc
flogo:update-app-release Update helm chart values for FLOGO application chart using values.yaml
flogo:update-app-release-endpoint-visibility Make an application endpoint public or private for helm managed apps. The API creates an ingress resource
with provided inputs - ingress class name, FQDN, path prefix, etc
flogo:upload-supplement Upload the supplement for a connector on the dataplane
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.
- 11d ago First seen · 118 lines · 34 tokens per session scan A e9c7b8a49118
tibco-platform-cli is a skill published in the GitHub repository TIBCOSoftware/flogo-enterprise-hub (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,496 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…