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/lovstudio/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/lovstudio/skills/design)<a href="https://agentmods.dev/plugins/lovstudio/skills/design"><img src="https://agentmods.dev/badge/plugins/lovstudio/skills/design/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/lovstudio/skills/design"><img src="https://agentmods.dev/badge/plugins/lovstudio/skills/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
design 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 16d 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": "design",
"source": "./",
"description": "Design — 10 free skills bundled together.",
"category": "Design",
"skills": [
"./skills/frontend-design",
"./skills/branding-consistency",
"./skills/maintain-partners",
"./skills/find-logo",
"./skills/professional-portrait",
"./skills/riso-portrait",
"./skills/mobile-infographic",
"./skills/business-card",
"./skills/gen-card",
"./skills/image-decorator",
"./skills/spectacular-ps"
],
"strict": false
}What it installs
The manifest is a name and a version. 10 skills travel with it, and installing the plugin installs all of them — 1,104 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill lov-maintain-partners A 294 tokens
- Skill lov-mobile-infographic A 110 tokens
- Skill lov-professional-portrait A 139 tokens
- Skill lov-business-card A 124 tokens
- Skill lov-find-logo A 99 tokens
- Skill lov-gen-card A 59 tokens
- Skill lov-image-decorator A 67 tokens
- Skill lov-branding-consistency A 70 tokens
- Skill lov-frontend-design A 71 tokens
- Skill lov-riso-portrait A 71 tokens
What ships with it
1 file beside marketplace.json#design 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.
- 16d ago Changed · -4 lines 75fa845edfd0
- 25d ago Changed · +3 lines 5fd766070f9c
- 1mo ago Changed · +1 lines 27746b8898ec
- 1mo ago Changed · +2 lines 95c82d51bd42
- 1mo ago First seen · 18 lines scan A b02f13c4482a
design is a plugin published in the GitHub repository lovstudio/skills (72 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
ultralytics-branding
Ultralytics brand guidelines (colors, Archivo font, naming, tone) for presentations, documents, marketing emails, social posts, and web designs.
frontend-design-skills
Design frontends, test interactions, and write clear interface copy.
visualcave
Design and render interactive technical diagrams as standalone HTML files or embeddable Astro/MDX components. Supports 11 Mermaid diagram types with dark mode, step-through reveal, hover highlighting, and one-click SVG/PNG/PDF export.
visualcave
Use when the user asks to create a diagram, chart, infographic, flowchart, architecture illustration, or any technical visualization. Outputs a self-contained HTML file using Mermaid.js.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.