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/permissions)<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/permissions"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/permissions.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.00036 | $0.02458 |
| Opus 5 | $0.00018 | $0.01229 |
| Sonnet 5 | $0.00007 | $0.00492 |
| Haiku 4.5 | $0.00004 | $0.00246 |
Grade A, and why
permissions 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/permissions — Custom Permission Model Generator
In-Process SDK only — custom permissions deploy inside the ACS JVM as part of the Platform JAR. They extend the global permission model; they are not a Share-tier concern.
Generate a custom permission model (permission groups + permissions) and optional dynamic authorities from requirements.
Input
Read REQUIREMENTS.md to identify permission requirements:
-
Resolve the Platform JAR project's
Root pathfrom Section 2 (Project Architecture).- If Section 2 contains no
Platform JARproject, stop and explain that/permissionsonly applies to the in-process Platform JAR project.
- If Section 2 contains no
-
Read Section 5 (Content Model Requirements) and any "Permission requirements" sub-section.
- Custom permissions are granted on a type or aspect — identify which custom type/aspect
(from
/content-model) the permission set applies to. If none is declared, ask the user to run/requirementsfirst (or provide a description as$ARGUMENTS).
- Custom permissions are granted on a type or aspect — identify which custom type/aspect
(from
-
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.my-extension). Read from<artifactId>in the platformpom.xmlor derive as{platform-artifactId}from Section 2. Never use the fullmodule.idproperty value as the directory name.{java-package}— the Java package declared in Section 2{prefix}— the namespace prefix declared in Section 5 (Content Model Requirements)
-
Derive from permission requirements:
{TypeOrAspect}— the qualified name the permission set is bound to (e.g.sc:document){PermissionGroup}— PascalCase permission group name (e.g.Publisher,Reviewer){Permission}— individual permission names (e.g.Publish,Withdraw)- Whether a dynamic authority is needed (a programmatic authority such as "the document's assigned reviewer") — generate one only if requirements call for it
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 · 254 lines · 36 tokens per session scan A 15ec93196e8e
permissions is a command published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,458 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-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.