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/flavien-ia/hypervibe-harness/_create-workflownpx skills add flavien-ia/hypervibe-harness --skill _create-workflowgit clone --depth 1 https://github.com/flavien-ia/hypervibe-harnessWrote 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/flavien-ia/hypervibe-harness/_create-workflow)<a href="https://agentmods.dev/skills/flavien-ia/hypervibe-harness/_create-workflow"><img src="https://agentmods.dev/badge/skills/flavien-ia/hypervibe-harness/_create-workflow.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.1 | $0.00059 | $0.04500 |
| Opus 5 | $0.00030 | $0.02250 |
| Sonnet 5 | $0.00012 | $0.00900 |
| Haiku 4.5 | $0.00006 | $0.00450 |
Grade A, and why
_create-workflow 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 6d 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.
const res = await fetch(input.documentUrl); How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Workflow - A finite intelligent pipeline inside the app
The brief you are invoked with
You are never reached by a user typing a command: add-automation (or add-ai)
has already decided that a workflow is the right shape, and hands you what it
learned. Do not re-run that decision, and do not re-ask what you were given.
| Field | What it carries |
|---|---|
TRIGGER |
user action / webhook / schedule |
STEPS |
the steps in order, and which of them need intelligence |
VOLUME |
how often it runs, how big the inputs are |
NAME |
the kebab-case name of the workflow |
Anything genuinely missing from the brief, you may ask (at most two questions). Anything present in it, you use as-is.
Communication
- Detect the user's language from the conversation (the user's own messages, anywhere in the session - not just this invocation: a bare slash command like
/bootstrapcarries no language signal by itself). If nothing in the conversation gives a signal, fall back to the OS locale (node -e "console.log(Intl.DateTimeFormat().resolvedOptions().locale)") before defaulting to English. ALWAYS reply in that language for every user-facing message: questions, progress, confirmations, summaries, errors - including any example text quoted in this skill, which is illustrative and must be translated, never sent verbatim. - Use plain, non-technical business language. Never expose internal script names (*.mjs) or jargon; describe actions in human terms. Say "workflow" and "step", never "pipeline runner" or "idempotency key" without a one-line explanation.
- When generating user-facing content for the scaffolded project (UI labels, emails, copy), write it in the user's language too.
- Show progress as a short natural-language checklist (in-progress and done states).
What a workflow is (and is not)
A workflow is a finite sequence of steps that the app itself executes when something happens: a user clicks, a file lands, a payment arrives, a schedule fires. Some steps are plain code (call an API, write to the database, send an email); some steps are intelligent (a model call that reads, classifies, extracts, or writes, through the project's AI brick). The whole run finishes in seconds to a couple of minutes, inside a normal serverless function.
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.
- 6d ago First seen · 378 lines · 59 tokens per session scan A 81f99bcac8e1
_create-workflow is a skill published in the GitHub repository flavien-ia/hypervibe-harness (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 4,500 once invoked, about $0.0003 per session on Opus 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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…