workflow

workflow is a command for Claude Code from aborroy/aiup-alfresco. It costs 43 tokens per session (6,117 once invoked), scanned A, original, Apache-2.0.

A generator for Alfresco workflows built with Activiti, a workflow engine that moves work through defined tasks and steps. It creates the process definition, task content model, registration, translations, and optional Java task listener.

In plain words
What is it for?
It helps define document or business processes with tasks, content fields, translated messages, and optional Java logic when a task runs.
Why use it?
It removes the repetitive setup involved in making a workflow available inside Alfresco and through its workflow API.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the aiup-alfresco plugin — 38 skills, 25 commands, 3 agents, 3 hooks shipped together

Good fit It helps define document or business processes with tasks, content fields, translated messages, and optional Java logic when a task runs.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/aborroy/aiup-alfresco/workflow
Install

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.

Clone the repo
git clone --depth 1 https://github.com/aborroy/aiup-alfresco

Made for: Claude Code.

Or install aiup-alfresco, the plugin that ships this one along with the rest of its 38 skills, 25 commands, 3 agents, 3 hooks.

Wrote 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.

agentmods badge for workflow

README.md
[![agentmods](https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/workflow/github.svg)](https://agentmods.dev/commands/aborroy/aiup-alfresco/workflow)
Your own site
<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/workflow"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/workflow/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.

agentmods 80×15 button for workflow

Your own site · 80×15
<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/workflow"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,117 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.06117
Opus 5 $0.00022 $0.03059
Sonnet 5 $0.00009 $0.01223
Haiku 4.5 $0.00004 $0.00612

Measured 7d ago against content hash 56f5b6e6ae58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 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.

commands/workflow.md · 533 lines

How it starts

The opening of the file, as written. The whole thing — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/workflow — Workflow Generator

In-Process SDK only — Activiti workflows deploy inside the ACS JVM as part of the Platform JAR. Share UI form configuration is out of scope for ACS 26.1 (use ADF/ACA for task forms). The generated workflow is fully operable via the Alfresco Workflow REST API v1.

Generate Alfresco Activiti workflow artefacts from requirements.

Input

Read REQUIREMENTS.md to identify workflow requirements:

  1. Resolve the Platform JAR project's Root path from Section 2 (Project Architecture).

    • If Section 2 contains no Platform JAR project, stop and explain that /workflow only applies to the in-process Platform JAR project.
  2. Read Section 7 (Behaviour Requirements) sub-section "Workflow requirements".

    • If no workflow requirements are listed in Section 7, stop and ask the user to run /requirements first (or provide a workflow description as $ARGUMENTS).
  3. From Section 2, derive:

    • {platform-project-root}. for Platform JAR only mode; {name}-platform/ for Mixed mode
    • {module-id} — the Platform JAR artifactId (bare artifact ID, e.g. workflows). Read from <artifactId> in the platform pom.xml or derive as {platform-artifactId} from Section 2. Never use the full module.id property value (e.g. com.someco.workflows) as the directory name.
    • {java-package} — the Java package declared in Section 2
    • {prefix} — the namespace prefix declared in Section 5 (Content Model Requirements)
  4. Derive from workflow requirements:

    • {processName} — camelCase process identifier (e.g. publishWhitepaper)
    • {ProcessName} — PascalCase process name (e.g. PublishWhitepaper)
    • {prefix}wf — workflow-specific namespace sub-prefix
    • User tasks, gateways, sequence flows, timer events, and service tasks as described

Output Files

All four artefacts below are required and must be generated together in a single run: the BPMN process definition, the workflow task content model XML, the Spring bootstrap registration, and the i18n message bundle. Never generate only a subset. The optional Java task listener (artefact 5) is generated only when the requirements describe custom Java logic in a task listener.

Read the full file on GitHub · 533 lines

Changes

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.

  1. 7d ago First seen · 533 lines · 43 tokens per session scan A 56f5b6e6ae58

Subscribe to this mod's changes

workflow is a command published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 6,117 once invoked, about $0.0002 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.