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/MAIAS-project/maiasWrote 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/plugins/maias-project/maias/plugin)<a href="https://agentmods.dev/plugins/maias-project/maias/plugin"><img src="https://agentmods.dev/badge/plugins/maias-project/maias/plugin/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/plugins/maias-project/maias/plugin"><img src="https://agentmods.dev/badge/plugins/maias-project/maias/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
maias 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 7d 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.
What it actually says
{
"name": "maias",
"description": "MAIAS (Mobile App Information Architecture Schema): create, edit, review, and wireframe app IA documents with validated, reference-safe operations. Four skills plus the maias MCP server in one install.",
"version": "0.5.1",
"author": {
"name": "Mark Chitty"
},
"homepage": "https://github.com/MAIAS-project/maias",
"repository": "https://github.com/MAIAS-project/maias-plugin",
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed d340335105e9
- 1mo ago First seen · 12 lines scan A 03bbddd40b9e
maias is a plugin published in the GitHub repository MAIAS-project/maias (1 stars, last pushed 8d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
sdlc-team-mobile
Shared mobile base — cross-platform mobile architecture and interaction UX agents. Install alongside sdlc-team-ios and/or sdlc-team-android.
swiftui-animation-match
Match UI/UX interaction needs to proven SwiftUI animation patterns from curated open-source catalogs, with system-first restraint. Ships an analyzed catalog of Shubham0812/SwiftUI-Animations (30 animations + 7 Metal shaders) and a repeatable recipe for cataloging more animation repos.
ios-hig-prototype
An iOS interface prototyping tool that produces a working interactive HTML mockup styled according to Apple’s Human Interface Guidelines, the design rules for Apple apps. It includes common phone interface parts such as navigation bars, tab bars, lists, and modals.
swiftui-native-component-design
A design process and ready-to-adapt Swift templates for building custom SwiftUI components that feel native — initializer shape, data flow, and ButtonStyle-like customization APIs.
mobile-design-skills
Mobile design skills for iOS Liquid Glass and Android Material 3 Expressive interfaces.
mobile-mvp-product
Skills for designing mobile MVPs in Figma, converting approved Figma designs into SwiftUI, and reviewing MVP scope for App Store readiness.