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 aborroy/aiup-alfresco --skill workflow-bpmn-validatorgit clone --depth 1 https://github.com/aborroy/aiup-alfrescoWrote 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/aborroy/aiup-alfresco/workflow-bpmn-validator)<a href="https://agentmods.dev/skills/aborroy/aiup-alfresco/workflow-bpmn-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/workflow-bpmn-validator/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/aborroy/aiup-alfresco/workflow-bpmn-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/workflow-bpmn-validator.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.00000 | $0.01280 |
| Opus 5 | $0.00000 | $0.00640 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
workflow-bpmn-validator 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow BPMN Validator
Validate the given Alfresco Activiti BPMN process definition (and companion workflow model, if present) against these rules.
BPMN Namespace Validation
- Root element must be
<definitions>with BPMN 2.0 namespace:xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" - REQUIRED:
xmlns:activiti="http://activiti.org/bpmn"— must be present; Alfresco Activiti extensions use this namespace - ERROR if present: Any
org.flowable.*class reference inclassattributes of<activiti:taskListener>,<activiti:executionListener>, or<serviceTask activiti:class="...">. ACS 26.1 uses Activiti 5.22.x; the Flowable API is not on the classpath.
Process Structure Validation
<process>element must have:idattribute (camelCase identifier)nameattribute (human-readable)isExecutable="true"
- WARNING if any
<startEvent>is missingactiviti:formKeyin a non-trivial process (more than one user task) - Every
<userTask>must have eitheractiviti:assigneeoractiviti:candidateGroups:- WARNING if a user task has neither — it will never be claimable
- WARNING if a user task that represents an approval step is missing
activiti:formKey
- Every
<exclusiveGateway>with multiple outgoing sequence flows must have<conditionExpression>on all but one outgoing flow:- ERROR if an outgoing flow from an exclusive gateway has no condition and is not marked as
default
- ERROR if an outgoing flow from an exclusive gateway has no condition and is not marked as
- Every
<serviceTask>must have eitheractiviti:classoractiviti:expressionoractiviti:delegateExpression:- WARNING for service tasks with none of these attributes (becomes a no-op)
Variable Naming Validation
- Scan all
<activiti:string>blocks inside<activiti:field name="script">elements and inside<conditionExpression>elements - ERROR if any call to
execution.setVariable(...)ortask.getVariableLocal(...)uses a variable name containing a colon (e.g.acme:outcome). The correct form uses underscore (acme_outcome). Alfresco maps content model properties{prefix}wf:{propName}→ process variable{prefix}wf_{propName}(colon → underscore). - ERROR if any
<conditionExpression>references a variable with a colon in the name (e.g.${acme:count == 2}). Use${acme_count == 2}.
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 · 79 lines · 0 tokens per session scan A 5499014d94f8
workflow-bpmn-validator is a skill published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,280 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
702-technologies-wiremock
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot…
coverage-enhancer
Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing…
edge-case-generator
Automatically identify potential boundary and exception cases from requirements, specifications, or existing code, and generate comprehensive test cases targeting boundary conditions, edge cases, and uncommon scenarios. Use this skill when analyzing programs, code repositories, functions, or APIs to discover and test…