I'd probably put it in modification discussion.
This for now.
Also I like the idea of a Model section, it would help improve the ties between modeling program-less scripters and modelers anyways. I imagine model-providing posts would need some structure though, like providing a mesh/bone Hierarchy as well as the name of each animation sequence provided (as well as if they're cyclic, blended, and whatnot). This stuff is usually hidden, although the animations can be exported as a .cs file just to give a scripter an easy list of sequence names to go by, still the information about the model itself apart from how it looks is limited unless the modeler tells everyone the specifics. That would be required.
It's a common problem that occurs in joint projects, it's the lack of communication because no one really knows what the forget to ask for and what the other person wants to do exactly. It's like for example, the scripter needs a very specific animation because he had a cool but complex idea in mind, but he doesn't know whether the modeler could do any of that stuff, or the modeler tries and fails to do it. Both of those risks are present so the scripters naturally don't even bother and many things are never realised.
Something like a Model section would push people to actually learn how to model properly, mostly like a competition and a chance to get their work rated. They would also get pointers on the models and new ideas on how to improve their overall skills. It would be a fantastic idea.