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 mattmre/EVOKORE-MCP-PUBLIC --skill workflow-templatesgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/workflow-templates)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/workflow-templates"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/workflow-templates/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/mattmre/evokore-mcp-public/workflow-templates"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/workflow-templates.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.00021 | $0.01816 |
| Opus 5 | $0.00010 | $0.00908 |
| Sonnet 5 | $0.00004 | $0.00363 |
| Haiku 4.5 | $0.00002 | $0.00182 |
Grade A, and why
workflow-templates 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 9d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAG-Based Workflow Templates
Reusable workflow definitions imported from Agent33's orchestration engine. Each template is a JSON file describing a directed acyclic graph (DAG) of steps that an orchestrator can execute with dependency awareness, parallel execution, conditional branching, and retry logic.
What Are DAG-Based Workflows?
A DAG workflow models a task as a graph of steps where:
- Dependency-aware execution -- Steps declare which other steps they depend on via
depends_on. The executor resolves the dependency graph and runs steps in topological order. - Parallel execution -- Steps that share no dependencies run concurrently up to a configurable
parallel_limit. - Conditional branching -- Steps with
action: "conditional"evaluate an expression and route execution throughthenorelsesub-step arrays. - Retry and timeout -- Each step can specify
retry.max_attempts,retry.delay_seconds, andtimeout_secondsfor resilience. - Input/output wiring -- Step outputs are referenced by downstream steps using template expressions like
${step_id.outputs.field}or{{ steps['step_id'].field }}.
Workflow JSON Schema
Every workflow file follows this top-level structure:
{
"name": "workflow-name",
"version": "1.0.0",
"description": "What this workflow does",
"triggers": {
"manual": true,
"on_event": ["event-name"],
"on_change": ["glob/pattern/**"],
"schedule": "cron-expression or null"
},
"inputs": {
"param_name": {
"type": "string|array|object",
"description": "What this input is",
"required": true,
"default": null
}
},
"outputs": {
"result_name": {
"type": "string|object|array",
"description": "What this output contains"
}
},
"steps": [ ... ],
"execution": {
"mode": "dependency-aware|sequential",
"parallel_limit": 4,
"continue_on_error": false,
"fail_fast": true,
"timeout_seconds": 300,
"dry_run": false
},
"metadata": {
"author": "agent-33",
"created": "2026-01-30",
"tags": ["tag1", "tag2"]
}
}
What ships with it
9 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.
- 9d ago First seen · 158 lines · 21 tokens per session scan A c5333af4c968
workflow-templates is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,816 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
stakeholder-alignment
Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use design-negotiation (designer-toolkit).
wrongstack-kanban
Record substantial project work on WrongStack's IPC-backed Kanban board so it survives the session and other agents can see it. Covers card detail, the managed Backlog→Todo→Running→Review→Done lifecycle, lease-fenced dispatch, and what "verified" means before a card reaches Done.
shared-monorepo-nx
Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management.
shared-monorepo-pnpm-workspaces
Skill "shared-monorepo-pnpm-workspaces" from agents-inc/skills, covering pnpm workspaces for monorepo management, critical: before using this skill, philosophy, core patterns and pattern 1: workspace configuration (pnpm-workspace.yaml).