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 permission-model-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/permission-model-validator)<a href="https://agentmods.dev/skills/aborroy/aiup-alfresco/permission-model-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/permission-model-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/permission-model-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/permission-model-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.00063 | $0.00647 |
| Opus 5 | $0.00032 | $0.00324 |
| Sonnet 5 | $0.00013 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
permission-model-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 10d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Permission Model Validator
Validate the given custom Alfresco permission model and dynamic authorities against these rules.
XML Structure Validation
- The file must be well-formed XML with root element
<permissions>. - Each
<permissionSet>must declare atypeattribute bound to a custom type or aspect ({prefix}:...), not a redefinition of a core type that removes built-in groups. - Each
<permissionGroup>and<permission>must declare aname.
Built-in Name Collision
- FLAG as ERROR any
<permissionGroup name="...">or<permission name="...">whose name collides with a built-in Alfresco permission group/permission:Read,Write,Delete,AddChildren,ReadProperties,ReadChildren,WriteProperties,Consumer,Contributor,Editor,Collaborator,Coordinator,SiteManager,SiteCollaborator,SiteContributor,SiteConsumer,FullControl,All.- Why it breaks: redefining a core group name corrupts the global permission model and can silently alter access across the whole repository.
- Fix: use a project-scoped PascalCase name; compose on top of a core group with
<includePermissionGroup permissionGroup="Read" type="cm:cmobject"/>.
Registration Validation
- The model must be registered as an extension model, not a replacement: look for a Spring
bean with
parent="permissionModelBootstrap"and amodelproperty pointing at thepermissionDefinitions.xmlunderalfresco/extension/.- WARN if no such registration bean is found in a companion
*-context.xml.
- WARN if no such registration bean is found in a companion
- The registering context must be imported from
module-context.xml.
Dynamic Authority Validation
- If a
*DynamicAuthority.javaexists:- It must
implements DynamicAuthority(fromorg.alfresco.repo.security.permissions). - It must implement
hasAuthority,getAuthority, andrequiredFor. - FLAG as ERROR
runAsSysteminsidehasAuthority(privilege escalation + per-node perf hazard). - WARN if
hasAuthoritydoes not guard withnodeService.exists(). - The bean must be registered (id
{prefix}.{name}DynamicAuthority) and added to the globaldynamicAuthoritieslist.
- It must
- WARN if a permission/group omits
requiresTypewhere it logically applies only to the bound type.
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.
- 10d ago First seen · 50 lines · 63 tokens per session scan A 5de6e1ec8d8e
permission-model-validator is a skill published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 647 once invoked, about $0.0003 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 skills, from other repositories
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
sns
AWS SNS notification service for pub/sub messaging. Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push.
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.