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/desirecore/market/workflownpx skills add desirecore/market --skill workflowgit clone --depth 1 https://github.com/desirecore/marketWhat 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.00054 | $0.06031 |
| Opus 5 | $0.00027 | $0.03016 |
| Sonnet 5 | $0.00011 | $0.01206 |
| Haiku 4.5 | $0.00005 | $0.00603 |
Grade A, and why
workflow 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 2d 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 — 660 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workflow Skill
L0: One-line Summary
Guides the Agent to design, edit, validate, test, and execute multi-node automated workflows via a DSL.
L1: Overview and Use Cases
Capability Description
workflow is a Procedural Skill that empowers the Agent to orchestrate multi-step automated workflows. Workflows are described by a YAML DSL file and are automatically executed by the engine in topological order.
Five base node types:
| Base | Purpose | Typical Scenario |
|---|---|---|
trigger |
Workflow entry point, declares input parameters | Manual trigger, webhook trigger |
code |
Executes code (JS/Python) | Data fetching, API calls |
llm |
Single LLM call (stateless) | Text generation, data analysis, summarization |
agent |
Invokes a full Agent (stateful) | Complex tasks requiring Agent memory, tools, and skills |
human_gate |
Waits for user confirmation | Approval of sensitive operations |
Use Cases
- The user wants to orchestrate repetitive multi-step work into an automated process
- The user needs multiple Agents to collaborate on a complex task
- The user needs to insert manual approval steps into an automated process
- The user wants to reuse and share validated workflows
Core Value
- Visual orchestration: The DSL description is clear and intuitive, with canvas visualization support
- Progressive construction: Write the skeleton first and gradually enrich it, reducing the chance of errors
- Safety gating: Use human_gate nodes to retain human decision-making authority at critical steps
- Reusability: DSL files can be archived, version-controlled, and shared across Agents
L2: Detailed Specification
Workflow SOP
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ 1. Understand│ ──→ │ 2a. Design │ ──→ │ 2b. Configure │ ──→ │ 3. Validate │
│ intent │ │ topology │ │ each node │ │ DSL │
└──────────────┘ │ (skeleton) │ │ (config/code) │ └──────────────┘
└──────────────┘ └──────────────┘ │
↓
┌──────────────┐ ┌──────────────┐
│ 5. Real run │ ←── │ 4. Dry-run │
└──────────────┘ │ testing │
└──────────────┘
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.
- 2d ago First seen · 660 lines · 54 tokens per session scan A 0b19b1bd5da1
workflow is a skill published in the GitHub repository desirecore/market (2 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 6,031 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-31.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
project-orchestration
Orchestrate multi-agent workflows for feature development using planning agents, context handoff, and stage management.
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
hex-release
Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflowdispatch) and manual release flows. Uses gitops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.
pr-review
Review a Pull Request for code quality, tests, merge conflicts, and readiness to merge.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…