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 fda-mappinggit 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/fda-mapping)<a href="https://agentmods.dev/skills/tibcosoftware/flogo-enterprise-hub/fda-mapping"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/fda-mapping/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/fda-mapping"><img src="https://agentmods.dev/badge/skills/tibcosoftware/flogo-enterprise-hub/fda-mapping.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.00120 | $0.07789 |
| Opus 5.5 | $0.00048 | $0.03116 |
| Sonnet 5.5 | $0.00024 | $0.01558 |
| Haiku 4.5 | $0.00012 | $0.00779 |
Grade A, and why
fda-mapping 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preflight: run
fda versionfirst (see AGENT.md → Prerequisites and preflight). If it fails, install/update the TIBCO Flogo VS Code extension (2.26.6+).
Making Flogo mappings with fda
The mapping task category in fda mirrors the Flogo VSCode mapping UI. Every field you can map in the UI's "Activity inputs" panel is reachable from the CLI; every source you can drag from the "Available data" panel has a dedicated discovery task.
This skill is the practical "how do I map X" reference. For the broader CLI surface see the flogo-design-assistant skill.
What you can map
Two distinct shapes — dmf enumerates both:
| Activity kind | Mapping path shape | Example |
|---|---|---|
Mapper (#mapper / tibco-wi-mapper) |
<flow>.<activity>.input.input.mapping.<dotted> |
MainFlow.MakeMapping.input.input.mapping.orderId |
| Any other activity (log, rest, sleep, …) | <flow>.<activity>.input.<field> |
MainFlow.LogIt.input.message |
For mappers, the leaf can be deeply nested (...mapping.shippingAddress.city). For non-mapper activities, the field comes from the activity's initActDef.activity.input schema (one level deep typically).
Mappable inputs vs settings (non-mapper activities)
Most non-mapper activities have BOTH mappable inputs AND configuration settings, all serialised under activity.input.<name> in the .flogo JSON. The Flogo VSCode UI shows them in two different tabs: "Activity inputs" (mappable) vs "Settings" (configuration). dmf mirrors this distinction.
The discriminator (read from each activity's descriptor in the bundled VSCode extension): a field is mappable when its descriptor entry has no display block OR display.mappable === true. Otherwise (has a display block but no mappable flag) → it's a setting, hidden from dmf.
For example, the Log activity has 4 input fields in the JSON — Log Level, flowInfo, message, logLevel — but dmf only shows message and logLevel, matching the UI. The other two are settings.
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 · 424 lines · 120 tokens per session scan A e702dad5b5c9
fda-mapping is a skill published in the GitHub repository TIBCOSoftware/flogo-enterprise-hub (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 120 tokens to every session and 7,789 once invoked, about $0.0005 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-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
deepstream-sop
Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…