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 content-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/content-model-validator)<a href="https://agentmods.dev/skills/aborroy/aiup-alfresco/content-model-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/content-model-validator.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.00060 | $0.01065 |
| Opus 5 | $0.00030 | $0.00532 |
| Sonnet 5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
content-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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Model Validator
Validate the given Alfresco content model XML against these rules:
Namespace Validation
- Namespace URI must follow the pattern
http://www.{company}.com/model/{prefix}/{version} - Namespace prefix must not collide with reserved Alfresco prefixes:
sys,cm,app,usr,act,wcm,wca,lnk,fm,dl,ia,smf,imap,emailserver,bpm,wcmwf,trx,stcp - Prefix must be lowercase alphanumeric, 2-6 characters
Structure Validation
- Root element must be
<model>withnameattribute in format{prefix}:modelName - Must contain
<namespaces>with at least one<namespace>declaration - If types are declared, they must be inside
<types>element - If aspects are declared, they must be inside
<aspects>element
Type and Aspect Validation
- Every
<type>must have anameattribute in format{prefix}:typeName - Every
<type>should declare a<parent>(default:cm:contentorcm:folder) - Property names must use the model prefix:
{prefix}:propertyName - Property
<type>must be a valid Alfresco data type:d:text,d:mltext,d:int,d:long,d:float,d:double,d:date,d:datetime,d:boolean,d:noderef,d:content,d:any,d:category,d:qname,d:locale,d:period
Mandatory Property Enforcement
- FLAG as ERROR any property that uses
<mandatory enforced="true">true</mandatory>.- Why it breaks:
enforced="true"makes ACS fire theIntegrityCheckerimmediately insideOnAddAspectPolicy, which runs beforeNodeServiceImpl.addAspect()has written the properties map to the database. The result is a spuriousIntegrityException: Mandatory property not seteven when the caller passes a fully-populated properties map. - Fix: Use
<mandatory>true</mandatory>(noenforcedattribute). The integrity check is then deferred tobeforeCommit, by which timeaddAspect()has written both the aspect and its properties. - Exception:
enforced="true"is safe only on properties belonging to types (not aspects), where the property must be supplied at node creation time via the REST API and is never set programmatically after the fact.
- Why it breaks:
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 · 66 lines · 60 tokens per session scan A fb154b135fc9
content-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 60 tokens to every session and 1,065 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
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.