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 glincker/claude-code-marketplace --skill workflow-composergit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/glincker/claude-code-marketplace/workflow-composer)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/workflow-composer"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/workflow-composer.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.00017 | $0.02772 |
| Opus 5 | $0.00009 | $0.01386 |
| Sonnet 5 | $0.00003 | $0.00554 |
| Haiku 4.5 | $0.00002 | $0.00277 |
Grade A, and why
workflow-composer 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 7d 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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Composer
⚡ UNIQUE FEATURE: First skill that lets you chain multiple Claude Code skills together into automated workflows with conditional logic, parallel execution, and error handling. Create complex automation pipelines with simple YAML configs.
What This Skill Does
Orchestrates multiple skills into powerful automated workflows:
- Chain skills together: Output of one skill becomes input to the next
- Parallel execution: Run multiple skills simultaneously
- Conditional logic: IF/THEN/ELSE based on skill results
- Error handling: Retry logic and fallback strategies
- Progress tracking: Real-time status of workflow execution
- Workflow templates: Save and reuse common workflows
- Schedule workflows: Run workflows on triggers or schedules
Why This Is Revolutionary
This is the first skill-composition framework for Claude Code:
- No coding required: Define workflows in simple YAML
- Visual workflow builder: Generate workflow configs interactively
- Reusable components: Build once, use everywhere
- Enterprise-ready: Error handling, logging, notifications
- Community workflows: Share workflows with others
Workflow Structure
name: my-workflow
description: What this workflow does
version: 1.0.0
# Input parameters
inputs:
project_path:
type: string
required: true
run_tests:
type: boolean
default: true
# Workflow steps
steps:
# Sequential steps
- name: generate-readme
skill: readme-generator
inputs:
path: ${inputs.project_path}
- name: generate-tests
skill: unit-test-generator
inputs:
target: ${inputs.project_path}/src
when: ${inputs.run_tests}
# Parallel execution
- name: quality-checks
parallel:
- name: security-scan
skill: security-auditor
inputs:
path: ${inputs.project_path}
- name: lint-code
skill: code-linter
inputs:
path: ${inputs.project_path}
# Conditional logic
- name: fix-issues
skill: auto-fixer
when: ${steps.quality-checks.security-scan.issues > 0}
inputs:
issues: ${steps.quality-checks.security-scan.results}
# Error handling
- name: deploy
skill: deploy-orchestrator
inputs:
environment: production
retry:
max_attempts: 3
backoff: exponential
on_failure:
- skill: rollback
- skill: notify-team
inputs:
message: "Deployment failed"
# Output mapping
outputs:
readme_path: ${steps.generate-readme.output.file_path}
test_coverage: ${steps.generate-tests.output.coverage}
security_issues: ${steps.quality-checks.security-scan.issues}
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.
- 7d ago First seen · 483 lines · 17 tokens per session scan A ce78f6043cac
workflow-composer is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,772 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-08-30.
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.
agent-orchestrator-v2
Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and…
Subagent Driven Development
Orchestrate specialized, autonomous AI agents to execute parallel subtasks with strict boundaries.
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.
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.
agent-orchestrator
Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and…