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 w8123/EnterpriseAgentFramework --skill workflow-ai-codinggit clone --depth 1 https://github.com/w8123/EnterpriseAgentFrameworkWrote 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/w8123/enterpriseagentframework/workflow-ai-coding)<a href="https://agentmods.dev/skills/w8123/enterpriseagentframework/workflow-ai-coding"><img src="https://agentmods.dev/badge/skills/w8123/enterpriseagentframework/workflow-ai-coding/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/w8123/enterpriseagentframework/workflow-ai-coding"><img src="https://agentmods.dev/badge/skills/w8123/enterpriseagentframework/workflow-ai-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.03670 |
| Opus 5.5 | $0.00034 | $0.01468 |
| Sonnet 5.5 | $0.00017 | $0.00734 |
| Haiku 4.5 | $0.00009 | $0.00367 |
Grade A, and why
workflow-ai-coding scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Use `curl.exe`, not the PowerShell `curl` alias: How it starts
The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow AI Coding
Operating Rules
Treat the ReachAI platform repository and live API responses as the source of truth. Do not edit runtime_workflow or runtime_workflow_resource_binding rows directly. All graph and binding changes go through Workflow AI Coding REST endpoints under /api/workflows/.../ai-coding.
凡是写入 ReachAI 或展示给业务用户的名称、标题、描述、说明、System Prompt、节点名称、审计原因、进度和结果,默认使用清晰的简体中文。不要仅因 API、Schema 或字段名为英文就生成英文业务文案。Token、MCP、AI、Agent、Supervisor、Workflow、Tool、API、SDK 等熟知专业术语,以及 keySlug、toolName、代码、路径、枚举值、协议字段和技术标识可保留英文;必要时使用“中文名称(英文术语)”。不要翻译或改写技术标识。
Core mental model:
GraphSpecis runtime semantics;canvas_jsonis layout only.- Create projects and lays out canvas from GraphSpec; patch defaults
layout.autoLayout=true. Thelayeredpolicy uses LR flow, 88px inter-layer boundary gaps, 56px same-layer gaps, and cycle-safe component packing. Before reporting back, confirmcanvas_json.nodes[].positionis non-overlapping and aligned; do not patch GraphSpec only and skip canvas synchronization. STARTandENDare Studio-only virtual canvas nodes. They never appear in GraphSpec nodes or edges.- Every workflow must set
graphSpec.entryNodeIdto a real node id and list every terminal node ingraphSpec.exitNodeIds. - Workflow AI Coding updates the Working Copy until an explicit publish request is made.
- Workflow AI Coding may publish a validated Working Copy through
POST /api/workflows/{workflowId}/ai-coding/publish; publish still runs release validation and creates an ACTIVEruntime_workflow_version. - Always read
GET .../contextbefore patching or publishing. Use the latestworkflow.updatedAtasbaseRevisionwhen saving and publishing. - First-class resource bindings may be replaced only while the Workflow is
DRAFT, throughPUT .../resource-bindingswith the latestbaseRevision. They are immutable after the first publish. - Node openness can be variant-specific. Read
nodeTypes[].enabledVariants; forINTERACTION, onlyPRESENT_OUTPUTis currently open. Do not infer thatCOLLECT_INPUT,USER_CHOICE,CONFIRM_ACTIONor other pause/resume variants are available merely because theINTERACTIONtype appears in the catalog. - Default patch behavior is
dryRun=true. Only setdryRun=falseafter validation passes.
What ships with it
4 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.
- 1mo ago First seen · 331 lines · 85 tokens per session scan A 42bd158df1f2
workflow-ai-coding is a skill published in the GitHub repository w8123/EnterpriseAgentFramework (945 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 3,670 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
omni-inference
The core OpenAI-compatible inference endpoints: chat completions, embeddings, images, audio (TTS/STT), moderations, rerank, and the Responses API. The primary integration surface for AI agents.
omni-providers
Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 374-provider catalog.
omni-auth
Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the OmniRoute API.
omni-combos-routing
Create and manage routing combos with 19 strategies (priority, weighted, round-robin, Auto-combo, and more). Configure fallback chains, test routing outcomes, and retrieve combo metrics.
omni-api-keys
Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.