Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TIBCOSoftware/flogo-enterprise-hubnpx agentmods add skills/tibcosoftware/flogo-enterprise-hub/flogo-unit-testingWrote 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-unit-testing)<a href="https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/flogo-unit-testing"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogo-unit-testing/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-unit-testing"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/flogo-unit-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00038 | $0.03417 |
| Opus 5.5 | $0.00015 | $0.01367 |
| Sonnet 5.5 | $0.00008 | $0.00683 |
| Haiku 4.5 | $0.00004 | $0.00342 |
Grade A, and why
flogo-unit-testing 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 13d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preflight (only needed when building / running tests): run
flogobuild version && flogobuild list-context && go versionfirst (see AGENT.md → Prerequisites and preflight, orpreflight.py --need build).flogobuild(Flogo App Build CLI) is downloaded from the TIBCO downloads page (not bundled in the VS Code extension), and building Flogo apps requires the Go runtime (go.dev/dl).
0. Configuration
All environment-specific values are defined in config.md. Read that file first for
FLOGO_APPS_DIR,FLOGOBUILD_PATH,FLOGOBUILD_CONTEXT_NAME, etc.
This skill creates unit tests for Flogo applications, runs them, and verifies all assertions pass.
It uses flogodesign-cli to create test files, test cases, assertions, and test suites,
then uses flogobuild test-app to execute the tests.
1. Inputs
The user must provide:
- Flogo app file path — the
.flogofile to test - Flows to test — which flows need test cases (or test all flows)
- Test data — sample input values for each flow (or derive from the API spec / activity configs)
2. Build Sequence
Step 1 — Analyze the app to identify flows and their inputs/outputs
flogodesign-cli.exe -f <AppName>.flogo describe-project
For each flow, determine:
- Flow name (e.g.
books_isbn_GET,books_POST) - Flow input types from
metadata.input(pathParams, body, headers, etc.) - Flow output types from
metadata.output(code, data) - What the Reply_to_API activity returns (the expected response data)
Step 2 — Create the test file
cd <FLOGO_APPS_DIR>
flogodesign-cli.exe -f <AppName>.flogo create-test-file
This creates <AppName>.flogotest in the same directory as the flogo file.
Step 3 — Create test cases for each flow
For each flow, create a test case with appropriate flow inputs.
flogodesign-cli.exe -f <AppName>.flogo create-test-case <TestCaseName> <FlowName> "<Description>" '<flowInputsJSON>'
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.
- 13d ago First seen · 360 lines · 38 tokens per session scan A f3020e9a02af
flogo-unit-testing is a skill published in the GitHub repository TIBCOSoftware/flogo-enterprise-hub (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 38 tokens to every session and 3,417 once invoked, about $0.0002 per session on Opus 5.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-10-17.
Other skills, from other repositories
agent-tester
Agent skill for tester - invoke with $agent-tester.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
dbt-transformation-patterns
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.