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 s5uy/ui-craftnpx agentmods add plugins/s5uy/ui-craft/marketplacegit clone --depth 1 https://github.com/s5uy/ui-craftGrade A, and why
vortex-ui-craft marketplace 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 2d 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": "vortex-ui-craft",
"owner": {
"name": "s5uy (Vortex)",
"email": "[email protected]"
},
"metadata": {
"description": "Premium UI/UX generation skills for Claude Code",
"version": "1.0.0"
},
"plugins": [
{
"name": "ui-craft",
"source": {
"source": "github",
"owner": "s5uy",
"repo": "ui-craft"
},
"description": "Premium UI/UX generation skill for Claude. Produces interfaces that feel handcrafted, restrained, and production-ready.",
"version": "1.0.0",
"author": {
"name": "s5uy (Vortex)",
"email": "[email protected]"
},
"homepage": "https://github.com/s5uy/ui-craft",
"repository": "https://github.com/s5uy/ui-craft",
"license": "MIT",
"keywords": ["ui", "ux", "design", "frontend", "react", "tailwind", "nextjs", "components"],
"category": "design"
}
]
}
What ships with it
1 file beside marketplace.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.
- 2d ago First seen · 33 lines scan A 3b23e8c2233e
vortex-ui-craft marketplace is a plugin published in the GitHub repository s5uy/ui-craft (4 stars, last pushed 4mo 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
flow-state marketplace
Plugin marketplace listing 4 plugins: youtube-to-markdown, imap-slim-mcp, chrome-control, firefox-control.
netresearch-branding
Netresearch brand guidelines with branded output styles.
section-508
Expert Section 508 compliance advisor for US federal ICT accessibility — VPAT/ACR completion, WCAG 2.0 AA audits, remediation planning, PDF accessibility, procurement language, keyboard and screen reader testing, undue burden assessments, and agency compliance workflows.
optim-agent
Optimize configurable systems against measurable objectives.
skill-based-architecture
Restructure oversized SKILL.md or scattered project rules into a well-organized Skill directory, with cross-tool thin shells, SessionStart hooks, Task Closure Protocol, and self-evolving workflows.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.