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.
/plugin marketplace add aomi-labs/skillsnpx agentmods add plugins/aomi-labs/skills/aomi-buildgit clone --depth 1 https://github.com/aomi-labs/skillsWrote 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/aomi-labs/skills/aomi-build)<a href="https://agentmods.dev/plugins/aomi-labs/skills/aomi-build"><img src="https://agentmods.dev/badge/plugins/aomi-labs/skills/aomi-build.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aomi-build 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 5d 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": "aomi-build",
"description": "Build new Aomi apps and plugins from API docs, OpenAPI/Swagger specs, SDK docs, runtime interfaces, or product requirements. aomi-build scaffolds production-ready Rust SDK crates (lib.rs, client.rs, tool.rs) with tool schemas, preambles, host-interop flows, and validation steps \u2014 turning a vendor's full API surface into AI-agent-callable tools. Same runtime that aomi-transact drives.",
"version": "0.10",
"author": {
"name": "aomi-labs",
"url": "https://aomi.dev"
},
"homepage": "https://github.com/aomi-labs/skills/tree/main/aomi-build",
"repository": "https://github.com/aomi-labs/skills",
"license": "MIT",
"keywords": [
"aomi",
"sdk",
"scaffold",
"openapi",
"rust",
"code-generation",
"agent-tools",
"developer-tools"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 244 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago First seen · 23 lines scan A 7006be289e26
aomi-build is a plugin published in the GitHub repository aomi-labs/skills (7 stars, last pushed 2d ago), licensed MIT. 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
contentful
Agent skills for Contentful apps, APIs, migrations, and personalization.
transformation
Digital maturity assessment, Now/Next/Later transformation roadmaps, target operating model design, technology strategy briefs, and transformation business cases.
architect-toolkit
Essential architect tools: katas, interview prep, review facilitation, mentoring, anti-patterns, audits, and pattern catalogs.
capacitor-core
Core Capacitor skills for best practices, plugin selection, and MCP automation.
agent-comms
Cross-harness LLM agent communication mesh — rooms, DMs, and presence.
ls-agent
Agent behavior skills.