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/intelligencedev/manifold/warpp-workflow-authoringnpx skills add intelligencedev/manifold --skill warpp-workflow-authoringgit clone --depth 1 https://github.com/intelligencedev/manifoldWrote 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/intelligencedev/manifold/warpp-workflow-authoring)<a href="https://agentmods.dev/skills/intelligencedev/manifold/warpp-workflow-authoring"><img src="https://agentmods.dev/badge/skills/intelligencedev/manifold/warpp-workflow-authoring.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.00103 | $0.02268 |
| Opus 5 | $0.00051 | $0.01134 |
| Sonnet 5 | $0.00021 | $0.00454 |
| Haiku 4.5 | $0.00010 | $0.00227 |
Grade A, and why
warpp-workflow-authoring 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 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.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring WARPP Workflows
WARPP is Manifold's typed-port dataflow engine. A workflow is a directed
acyclic graph of nodes. Data moves only through typed wires or literals —
there are no expressions. Your job is to produce a valid workflow document
(JSON) and prove it valid with workflow_save.
The one rule
Every node is a pure function with declared, typed input and output ports. An input binding is exactly one of:
{"from": "nodeID.port"}— a wire from an upstream node's output port{"value": <literal>}— a fixed literal typed into the node
Never both. Never an expression string, template, or ${...}. To reshape data,
use a data node (data.extract, data.template, data.parse, …).
The authoring loop (do this every time)
- Discover tools with
tool_search. For every step that performs an external action (web search/fetch, file I/O, calling an API or another agent, sending a message, RAG, an MCP capability, …), calltool_searchwith a natural-language description of the capability you need — e.g."search the web","read a file","query a database","send a slack message". The user may have configured MCP servers that publish tools you cannot know ahead of time, so do not assume a tool exists or guess its name — search, then pick the best-matching result for the step. If several match, choose the most specific/appropriate one. workflow_catalog— fetch the live node manifests for the tools you chose (plus the builtins), their exact port names/types, and the coercion table. Every registry tool is available as a node typedtool.<name>. Never guess a node type or a port name — read them from the catalog.- Build the document (shape below). Prefer wiring (
from) over literals for anything that should be dynamic. workflow_save— it validates and returns diagnostics. If any come back, fix each one (they carry acode,message, andpath) and save again. Do not stop until it saves with no error diagnostics.workflow_run(only if asked to test) — runs it and returns the declared outputs.
What ships with it
1 file 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.
- 6d ago First seen · 165 lines · 103 tokens per session scan A 2cddf9e87afb
warpp-workflow-authoring is a skill published in the GitHub repository intelligencedev/manifold (497 stars, last pushed 28d ago), licensed MIT. It adds 103 tokens to every session and 2,268 once invoked, about $0.0005 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
release-notes
Draft concise release notes.
adr-skill
Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses…
add-harness-package
Guide for adding new AI SDK harness packages. Use when creating a new @ai-sdk/harness- package that adapts a coding-agent runtime to HarnessV1.
add-provider-package
Guide for adding first-party AI provider packages to the AI SDK. Use when creating a provider package under packages/ to integrate an external AI service.
migrate-ai-sdk-v6-to-v7
Migrate applications from AI SDK 6.x to AI SDK 7.0. Use when upgrading Vercel AI SDK packages, fixing v7 migration errors, or when the user mentions AI SDK v6, v7, upgrade, migration, breaking changes, system to instructions, fullStream, telemetry, tool context, or finalStep.
update-provider-models
Add new or remove obsolete model IDs for existing AI SDK providers. Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue. Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs".