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/alexmond/alexmskillsWrote 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/alexmond/alexmskills/screenshot-sweep)<a href="https://agentmods.dev/plugins/alexmond/alexmskills/screenshot-sweep"><img src="https://agentmods.dev/badge/plugins/alexmond/alexmskills/screenshot-sweep.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
screenshot-sweep 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": "screenshot-sweep",
"description": "Read the whole screenshot, not just the bug you came for. Sweeps every capture against a checklist of UI defects, files what it finds, and grows the checklist each time a defect is reported that it should have caught.",
"version": "1.1.0",
"author": {
"name": "Alex Mondshain",
"email": "[email protected]"
},
"homepage": "https://www.alexmond.org/alexmskills/",
"repository": "https://github.com/alexmond/alexmskills",
"license": "MIT",
"keywords": [
"screenshot",
"ui",
"review",
"self-learning",
"accessibility",
"visual-regression"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 128 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.
- 2d ago First seen · 21 lines scan A a9d7c4151be0
screenshot-sweep is a plugin published in the GitHub repository alexmond/alexmskills (6 stars, last pushed yesterday), 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-05.
Other plugins, from other repositories
visual-documentation-plugin
Skills for creating stunning visual HTML documentation with modern UI design, SVG diagrams, flowcharts, dashboards, timelines, technical documentation, and comprehensive project architecture diagrams.
code-operations-plugin
Skills for code manipulation operations including line-based code transfer, bulk refactoring, and file analysis - converted from code-copy-mcp.
agent-skills
Skills for the parts of shipping that code review never covers: the loading states, the type scale, and whether half the diff is AI slop.
design-assets
Generate colour palettes, favicon packages, custom SVG icon sets, and image processing (resize, convert, optimise).
frontend
Tailwind v4 theming and shadcn/ui component installation, customisation, and recipes.
html-showcase
Canonical CSS kernel + HTML skeleton for static showcase pages (provenance reports, contractor portfolios, telemetry dashboards). Single design-system SSoT served via jsDelivr CDN; pages stay pure HTML with optional per-page CSS overrides.