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 agentmods add skills/eric-cielo/moflo/connector-buildernpx skills add eric-cielo/moflo --skill connector-buildergit clone --depth 1 https://github.com/eric-cielo/mofloWrote 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/eric-cielo/moflo/connector-builder)<a href="https://agentmods.dev/skills/eric-cielo/moflo/connector-builder"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/connector-builder.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.02326 |
| Opus 5 | $0.00026 | $0.01163 |
| Sonnet 5 | $0.00011 | $0.00465 |
| Haiku 4.5 | $0.00005 | $0.00233 |
Grade A, and why
connector-builder 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 4d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connector Builder
Purpose: scaffold production-ready step commands (StepCommand) and, when truly needed, generalized I/O connectors (SpellConnector) with proper types, tests, and registration.
Read First — Companion Files
| File | When to read |
|---|---|
| templates/connector.md | When generating a generalized connector — full source + test + registration scaffold |
| templates/step-command.md | When generating a step command — full source + test + registration scaffold |
| ../spell-builder/architecture.md | Always — three-layer model and connector-vs-step decision tree |
| ../spell-builder/permissions.md | When defining capabilities — required disclosure format |
| ../spell-builder/preflight.md | When authoring preflight checks — copywriting rules for user-visible reason strings |
Prerequisites
- MoFlo project with
cli/spellspackage - TypeScript 5+
- Vitest for testing
What This Skill Does
- Guides you through building a step command (spell step logic) or, rarely, a generalized connector (new I/O transport)
- Generates type-safe TypeScript implementing the correct interface
- Creates a test file with vitest mocks
- Shows how to register the component and use it in spell YAML
Quick Start
Ask the user:
What do you want to build?
- Step command — executes logic within a spell step (transform data, control flow, etc.)
- Generalized connector — wraps a new I/O transport type (e.g., WebSocket, gRPC, MQTT)
Important: Simple service integrations (Slack webhook, S3 upload, Jira comment) should compose existing connectors (http, github-cli, playwright) in spell YAML — no dedicated connector needed. However, platforms requiring complex multi-step browser interaction (like Outlook.com web UI) DO warrant a dedicated connector. See ../spell-builder/architecture.md for the decision tree.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 214 lines · 53 tokens per session scan A 3c44517aca73
connector-builder is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,326 once invoked, about $0.0003 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.