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.
git 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/commands/aborroy/aiup-alfresco/events)<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/events"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/events.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.01038 |
| Opus 5 | $0.00009 | $0.00519 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
events 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/events — Out-of-Process Event Listener Generator
Generate a Spring Boot Out-of-Process application that consumes Alfresco repository events via ActiveMQ.
/scaffold must run first. This command augments the existing Event Handler project; it must not
invent a second project layout or merge event-listener code into the Platform JAR project.
When to use
Use this command for asynchronous, reactive integrations: notifications, external system sync, workflow triggers based on content changes.
Do NOT use for:
- Synchronous content validation → use
/behaviours(In-Process) - REST API exposure → use
/web-scripts(In-Process) - On-demand triggered logic → use
/actions(In-Process)
Input
Read REQUIREMENTS.md to identify event-driven integration requirements and resolve the
Event Handler project's Root path from Section 2 (Project Architecture).
- If Section 2 contains no
Event Handlerproject, stop and explain that/eventsonly applies to an out-of-process Spring Boot project. - If Section 2 contains both Platform JAR and Event Handler projects, write files only under the
Event Handler
Root path(typically{name}-events/), never under the Platform JAR module or the aggregator root.
Output Files
1. Spring Boot Application
{event-project-root}/src/main/java/{package}/{Name}Application.java
- Expected to exist already from
/scaffold; create only if missing @SpringBootApplication
2. Event Handler
{event-project-root}/src/main/java/{package}/handler/{Name}EventHandler.java
- Annotate with
@AlfrescoEventListener - Filter by node type or aspect where applicable
- Log at
INFOlevel on successful processing;ERRORon failure - Configure a dead-letter queue for error handling
3. Application Properties
{event-project-root}/src/main/resources/application.properties
spring.activemq.broker-url=${SPRING_ACTIVEMQ_BROKER_URL:tcp://localhost:61616}
spring.activemq.user=${SPRING_ACTIVEMQ_USER}
spring.activemq.password=${SPRING_ACTIVEMQ_PASSWORD}
alfresco.events.defaultExchangeName=alfresco.repo.event2
- Expected to exist already from
/scaffold; update only if required properties are missing
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.
- 8d ago First seen · 101 lines · 17 tokens per session scan A 14c64f59fc06
events is a command published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,038 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 commands, from other repositories
design-api-integration
Design an integration with a third-party API so its failures and changes stay contained.
design-caching
Design a caching layer with explicit invalidation, chosen for a specific access pattern rather than added generally.
api-contract
Write a human-readable API contract companion as Markdown in the user's repository. Use when invoked as /document-design-system:api-contract. Produce designed HTML or PDF only when asked.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.