It so depends on what the package and agent are. Can you provide some more information? Sometimes, we can just upload a .pkg and set a policy to install it, sometimes we have to create an installer to deal with what the developer didn’t, and sometimes we can just pick a package out of app installers. 

With a little more detail I’m sure we can point you in a good direction. 

We definitely need more details to help you with this. For some of the agents that I install, I have to stage the installer for the agent in a temp folder somewhere and then have a script run the install and configuration process. I do this with Tanium. I create a package that stages the Tanium installer package and a configuration file in a temp folder. The script that is part of the policy runs after the installer package and configuration file are staged. It runs the installer package and then configures the newly installed agent. I use Composer to create the package that places the Tanium installer and configuration file in the temp folder. Once you figure out a good process, you should test, test, test, and then test again to make sure it works. Create a smart group to track how many computers have the agent installed. You may also need an extension attribute depending on where the agent installs and what kind of data you need to track successful installs. I’m happy to share some examples with you.