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/artemnovichkov/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/artemnovichkov/skills/design-compare)<a href="https://agentmods.dev/plugins/artemnovichkov/skills/design-compare"><img src="https://agentmods.dev/badge/plugins/artemnovichkov/skills/design-compare/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/artemnovichkov/skills/design-compare"><img src="https://agentmods.dev/badge/plugins/artemnovichkov/skills/design-compare.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
design-compare 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 1mo 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-compare",
"description": "Compare Figma designs against implementation screenshots with interactive HTML reports",
"version": "1.2.0",
"author": {
"name": "Artem Novichkov",
"email": "[email protected]",
"url": "https://artemnovichkov.com"
},
"keywords": [
"figma",
"design",
"screenshot",
"comparison",
"ui"
],
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 74 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.
- 1mo ago Changed · +13 lines 7079748d5afc
- 1mo ago First seen · 6 lines scan A ac1ed56f8c1d
design-compare is a plugin published in the GitHub repository artemnovichkov/skills (40 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-30.
Other plugins, from other repositories
test-writing
Generate and validate PHPUnit tests for Shopware 6. Unit tests: analyzes source classes to detect category (DTO, Service, Flow/Event, DAL, Exception) and applies category-specific templates. Migration tests: analyzes SQL operations to generate pattern-appropriate migration tests with 8 migration-specific rules.…
dev-tooling
Three MCP servers for PHP and JavaScript operations. PHP (php-tooling): PHPStan, ECS, Rector, PHPUnit, PHPUnit coverage gap analysis, Symfony Console. Administration (js-admin-tooling): ESLint, Stylelint, Prettier, Jest, TypeScript, Vite builds. Storefront (js-storefront-tooling): ESLint, Stylelint, Jest, Webpack…
implementation
Disciplined implementation stage: execute approved plans inline (/implementation:implement) or via orchestrated worker subagents (/implementation:implement-dispatch) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back.
evals
LLM evaluation methodology and eval-suite design, based on Anthropic's evaluation guidance. /evals:methodology answers questions on success criteria, eval design, and grading. /evals:design interviews for measurable success criteria and scaffolds a graded eval suite for an LLM app or Claude Code skill.…
miro
Miro board management over the Model Context Protocol: create and manage boards, sticky notes, shapes, frames, connectors, and tags for EventStorming, brainstorming, and diagramming. Ships a local stdio MCP server that installs its pinned npm dependencies on first launch (needs Node.js 24+ and npm); installs disabled.
mutation-testing
Measures whether a test suite can actually detect faults, not merely execute code: /mutation-testing:principles answers operator, mutant-state, and metric questions from the primary literature; /mutation-testing:setup verifies the ecosystem's mutation tool and writes the tracked config; /mutation-testing:audit ru.