Dynamic workflows for the agent tool you already use.

Describe a process in plain language. The Model Context Protocol (MCP) host you already work in authors the workflow, validates it without spending tokens, and runs it. You choose the Agent Client Protocol (ACP) agent and model for every call.

“Implement the change, review it, revise it.”from your MCP host · agent CLI or editor

agentprism-workflows validatestatic parse · dry run · config probe · 0 tokens

AgentPrism

codex · gpt-5.6-solimplementation

parallel()

claude · opus[1m]correctness review

pi · moonshotai/kimi-k3product-truth review

structured resultrun kx7f-2mqarun · inspect · await · stop

gate()changes requested → implementation attempt 2

  1. “Implement the change, review it, revise it.”from your MCP host · agent CLI or editor
  2. agentprism-workflows validatestatic parse · dry run · config probe · 0 tokens
  3. codex · gpt-5.6-solimplementation
  4. parallel()
    claude · opus[1m]correctness reviewpi · moonshotai/kimi-k3product-truth review
  5. structured resultrun kx7f-2mqarun · inspect · await · stop
  6. gate()changes requested → implementation attempt 2

Add one MCP server. Keep your tool.

Register AgentPrism in an agent CLI, editor, or other MCP host. The host receives the workflow tool, plus theauthor-workflow prompt when it supports MCP prompts.

primary MCP setup · register in your MCP host
npx -y @automatalabs/workflows mcp

MCP host configuration

{
  "command": "npx",
  "args": ["-y", "@automatalabs/workflows", "mcp"]
}

What you need

  • Node.js 22 or newer
  • an MCP host
  • an authenticated backend agent CLI

AgentPrism bundles the Claude, Codex, and pi backends. OpenCode requires a separate opencode installation. Authenticate only the backends you route calls to.

Equivalent standalone server: npx -y @automatalabs/mcp-server

Open source under Apache-2.0. Verify the releases

Describe the process. The host agent writes it.

Give the host agent the published skill or the MCP prompt. Your request becomes a runnable workflow script: real JavaScript, and every implementation and review prompt includes your original request.

Request to the MCP host

“Implement the approved change. Run two independent reviews. If either reviewer requests changes, start a new implementation attempt.”
Published skill
npx skills add agentprism/agentprism-workflows
MCP prompt
author-workflow
Validate without agent tokens
agentprism-workflows validate implementation-review.workflow.js
Inspect the authoring skill

abridged · implementation-review.workflow.js

export const meta = {
	name: 'implementation-review',
	phases: [{ title: 'Implement' }, { title: 'Review' }],
};

phase('Implement');
const outcome = await gate(
	(feedback, attempt) =>
		agent(`Implement attempt ${attempt + 1}. Run the relevant checks.`, {
			model: 'codex/gpt-5.6-sol',
			configOptions: { reasoning_effort: 'max' },
		}),
	async (implementation) => {
		phase('Review');
		const reviews = await parallel([
			() =>
				agent('Review this implementation for correctness…', {
					model: 'claude/opus[1m]',
					schema: VERDICT,
				}),
			() =>
				agent('Review this implementation for product truth…', {
					model: 'pi/moonshotai/kimi-k3',
					schema: VERDICT,
				}),
		]);
		// a changes-requested verdict starts implementation attempt 2
	},
	{ attempts: 3 },
);

Cost and quality, decided per call.

Routing is part of the workflow script. Pick a lower-cost route for bounded work, a stronger route for critical review, or a different provider for independent verification. AgentPrism never substitutes a similar model when a named route is unavailable.

agent() · implementationcodexgpt-5.6-solwrite-capable route
agent() · correctness reviewclaudeopus[1m]independent provider
agent() · product-truth reviewpimoonshotai/kimi-k3independent provider
agent() · optional routed callopencodeseparate installation required
agent() · specialized callcustom ACP agentregistered by the host

Probe the exact models, modes, and options before a run spends agent tokens: agentprism-workflows config. We recorded the model strings above from the live configuration catalog on 2026-07-22. Verify routing in the workflows guide

Keep control when a run outlives the turn.

Run in the foreground or background. Inspect current state, await for a bounded interval, stop the whole run or one in-flight call, and resume a new run from the completed work in the durable journal.

inspect
read status, result, and bounded run log
await
wait for a bounded interval
stop
stop a run or one in-flight call
resumeFromRunId
start a new run from journaled work
checkpoint()
record a human decision inside the run
example durable journal · ~/.agentprism/workflows
run IDworkflowstatuscallsupdated
kx7f-2mqaimplementation-reviewpaused · quota3 / 514:32
m2rc-8pvnimplementation-reviewresumedreplay · 0 current provider tokens4 / 514:36
q1tm-4hksimplementation-reviewcomplete5 / 514:41

Durability has limits. Background work does not survive MCP server process exit, host disconnect, crash, or machine loss: in-flight work stops and only the journaled prefix stays resumable. Replay guarantees journal and workflow-script integrity, not filesystem or external state. Provider quota limits or authentication failures pause a managed run instead of failing it. Verify the run-control contract

Give your agent tool a process it can run.

Connect the MCP server, follow the first-workflow tutorial, and inspect the public source behind every claim on this page.

start here · primary MCP setup
npx -y @automatalabs/workflows mcp