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/requirements)<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/requirements"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/requirements.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.00016 | $0.01779 |
| Opus 5 | $0.00008 | $0.00890 |
| Sonnet 5 | $0.00003 | $0.00356 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
requirements 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/requirements — Requirements Gathering
You are helping the user define requirements for an Alfresco Content Services extension.
Given the user's description in "$ARGUMENTS", produce a structured requirements document.
Architecture Decision (ask first)
Before writing any section, ask the following architecture questions if the description does not make the answers obvious. Record the answers — they determine the whole project structure.
Q1 — Synchronous or asynchronous reaction?
"Does this feature need to react within the same transaction as the user action (e.g. reject an upload, enforce a rule, return an immediate API response)? Or can it react after the fact, asynchronously (e.g. send a notification, trigger an integration, update an analytics system)?"
Q2 — Does it expose a repository REST API or web script?
"Does the feature need to expose a custom REST endpoint served by the ACS JVM itself?"
Q3 — Does it need a multi-step approval workflow?
"Does this feature need to route content or tasks through multiple human approval steps, with assignee groups, parallel reviews, outcome decisions (approve/reject), timer escalations, or similar process orchestration?"
Q4 — Does it need to customize the legacy Share UI itself?
"Does this feature need Share-tier artefacts such as
share-config-custom.xml, Share forms, Surf pages/components, Aikau pages/widgets, dashlets, or evaluators?"
Q5 — Is the UI target really Share, or should it be treated as a modern external frontend?
"If a user interface is needed, is the target the legacy Share web tier specifically? Or should this be treated as ACA/ADF/custom frontend work that consumes ACS APIs without deploying Share addon artefacts?"
Project-selection rules (use to populate Section 2 — Project Architecture):
| Need | Add this project |
|---|---|
| Same-transaction repository logic, ACS-hosted REST/Web Script, or workflow | Platform JAR |
| Legacy Share-tier UI customization | Share JAR |
| Asynchronous event-driven processing | Event Handler |
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 · 155 lines · 16 tokens per session scan A 3f2861aebbf3
requirements is a command published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,779 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
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
runs
List live and persisted CCAM-launched Claude Code and Codex runs.
project-health
Audit and manage project configuration — permissions, context, docs.
stat
A project-status command for an embedded-software project. It reads saved project notes and shows the current state, progress, next action, or a fuller project overview.
rec
A project-recovery command that reads a small set of status files and shows the current work and next action.
status
Command "status" from ngocsangyem/MeowKit, covering /mk:status — delivery status report, usage, behavior, execution steps and skip conditions.