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 Xircth/vibex-plugin-workflow-creator --skill vibex-workflow-creatorgit clone --depth 1 https://github.com/Xircth/vibex-plugin-workflow-creatorWrote 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/xircth/vibex-plugin-workflow-creator/vibex-workflow-creator)<a href="https://agentmods.dev/skills/xircth/vibex-plugin-workflow-creator/vibex-workflow-creator"><img src="https://agentmods.dev/badge/skills/xircth/vibex-plugin-workflow-creator/vibex-workflow-creator/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/xircth/vibex-plugin-workflow-creator/vibex-workflow-creator"><img src="https://agentmods.dev/badge/skills/xircth/vibex-plugin-workflow-creator/vibex-workflow-creator.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.00042 | $0.00644 |
| Opus 5 | $0.00021 | $0.00322 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
vibex-workflow-creator 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeX Workflow Creator
Use this Skill when the user asks to create or change a VibeX Workflow. The source artifact is the fact. An in-memory graph, a Studio screenshot, or a conversation outline is not.
Source artifact
- Find or create exactly one
*.vibex-workflow.jsonfile, either project-relative or below~/.vibex/workflows/. - Read an existing artifact with
workflow_source_readbefore editing and keep its revision. - Save with
workflow_source_writeand that revision. On conflict, read again and reconcile. Never overwrite blindly.
Graph rules
- Model nodes as durable steps, not as Agents. An Agent Step owns one child Conversation; retries and continuation add Turns to that same Conversation.
- Give every step a stable kebab-case ID. Encode ordering only through
dependsOn. Never create a cycle or reference a missing step. - Use
inputBindingsand JSON Pointers for data flow. outputSchemais an example embedded into the initial prompt. It does not validate or block the final Assistant text. Downstream steps receive that text even when it is not valid JSON.- Select
executorProfileId,modeOverride, andconfigOverridesfrom the Agent's native session controls. Do not invent Workflow-specific permission modes. - Omit scheduling metadata unless the user asks for a workspace-isolation strategy. Use
completionPolicy: manualonly when the user wants a confirmation gate after the Agent Step.
Debug versus publish
Save and validate before any test.
workflow_debug_sourcetests the current unpublished source through a hidden durable snapshot. It must not publish a version or retarget an Automation.- Later attempts pass
parentRunId. Usenodeto isolate one node, ordownstreamto keep unchanged completed ancestors and rerun the selected branch. workflow_publishcreates an immutable visible version, and only when the user asks for a release.workflow_startruns a published version against a real VibeX workspace ID.workflow_debug_from_stepdebugs an already-published version.
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.
- 8d ago First seen · 49 lines · 42 tokens per session scan A 0e95a200a84c
vibex-workflow-creator is a skill published in the GitHub repository Xircth/vibex-plugin-workflow-creator (0 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 644 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…