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 flogobuildgit 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/flogobuild)<a href="https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/flogobuild"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogobuild/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/flogobuild"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogobuild.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 29 This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.Fix: Remove or rewrite any text that instructs the agent to ignore prompts, override safety rules, or trust unverified content. Ensure skill content cannot be injected to alter agent behavior.
- high Prompt Injection · line 60 This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.Fix: Remove or rewrite any text that instructs the agent to ignore prompts, override safety rules, or trust unverified content. Ensure skill content cannot be injected to alter agent behavior.
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.00021 | $0.00614 |
| Opus 5 | $0.00010 | $0.00307 |
| Sonnet 5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
flogobuild 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 10d 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.
What it actually says
flogobuild
Command-line utility for building executable and Docker image for TIBCO Flogo® applications
Usage:
flogobuild [command]
Available Commands:
build-docker-image Build Flogo application Docker image
build-exe Build Flogo application executable
build-tp-deployment Build TIBCO Platform deployment zip for the Flogo application
create-context Create context for building and packaging Flogo applications
delete-context Delete existing context
help Help about any command
list-context List available contexts
package-docker-image Package existing Linux based Flogo application executable as docker image
set-default-context Set one of the configured context as default for building and packaging Flogo applications
test-app Test Flogo application
version Print the version
Flags:
--debug Enable debug mode for detailed logging
-h, --help help for flogobuild
--verbose Enable verbose mode for additional output
Use "flogobuild [command] --help" for more information about a command.
To get help on a specific command run:
flogobuild [command] -h
To build an executable for testing run:
flogobuild build-exe -h
Build Flogo application executable
Usage:
flogobuild build-exe [flags]
Flags:
-f, --app-json-file string Path for FLOGO application file(.json/.flogo)
-c, --context-name string Name of the context to used for building app. If not provided, default context will be used
-n, --exe-name string Name of the executable file. If not provided, app name will be used as executable file name
-h, --help help for build-exe
-o, --output-directory string Directory where executable file to be created. If not provided, executable will be created in the current directory
-p, --platform string Platform(OS) type for the app executable. Specify value in GOOS/GOARCH format. e.g ["linux/amd64","windows/amd64","darwin/amd64","darwin/arm64"]. If not provided, app will be build for current platform where CLI is running. Refer https://go.dev/doc/install/source#environment for supported platforms.
Global Flags:
--debug Enable debug mode for detailed logging
--verbose Enable verbose mode for additional output
Build context: Use the build context configured for your Flogo version. List available contexts with
flogobuild list-context. The context name typically follows the patternflogo-<version>-<build>(e.g.flogo-2.26.0-1789). Set this in your project'sCLAUDE.mdso the agent uses the right one.
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.
- 10d ago First seen · 64 lines · 21 tokens per session scan A 4146a56886e5
flogobuild is a skill published in the GitHub repository TIBCOSoftware/flogo-enterprise-hub (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 614 once invoked, about $0.0001 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
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
holoscan-install-container
Install Holoscan SDK via the NGC Docker container. Use for container-based installs; not for native apt/pip/Conda installs.
doca-argus
Use this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operational anomalies, and forwards findings to a SIEM (Splunk / ELK / Sentinel /…
doca-urom-svc
Operate the DOCA UROM Service container on BlueField Arm for remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using doca-urom: pull the NGC image, choose the UCX component, size queues, configure Comch pairing, and align host and service versions. SECURITY: the service has no…