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/Shilo/pixellab-pipWrote 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/shilo/pixellab-pip/gemini-extension)<a href="https://agentmods.dev/plugins/shilo/pixellab-pip/gemini-extension"><img src="https://agentmods.dev/badge/plugins/shilo/pixellab-pip/gemini-extension/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/shilo/pixellab-pip/gemini-extension"><img src="https://agentmods.dev/badge/plugins/shilo/pixellab-pip/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pixellab-pip 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 yesterday.
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": "pixellab-pip",
"version": "2.2.0",
"description": "Routes PixelLab asset/API requests across MCP, REST v2, website/editor workflows, Aseprite, Pixelorama, and legacy v1.",
"license": "MIT",
"contextFileName": "GEMINI.md"
}
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.
- yesterday Changed 2316c80e653e
- 5d ago Changed 71a3143e1c31
- 21d ago Changed a730a28d586a
- 1mo ago First seen · 8 lines scan A 77fbe85de128
pixellab-pip is a plugin published in the GitHub repository Shilo/pixellab-pip (37 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-09.
Other plugins, from other repositories
better-harness
Build an AI-ready engineering system for safe coding-agent delivery and continuous software improvement.
reporting-and-database-access
Database Toolbox, MATLAB Report Generator, Parallel Computing Toolbox, and Simulink Report Generator.
matlab-agentic-toolkit
Core MATLAB skills and MCP tools for AI coding agents. Testing, debugging, code review, Live Scripts, App Builder, and code modernization.
wavedash
Build browser games, integrate the Wavedash SDK, and prepare builds for upload and publishing.
apple-dev-skills
Apple, SwiftPM, Xcode, macOS privacy, file access, entitlement, and virtualization workflows.
apple-creator-studio-skills
Apple Creator Studio workflows for production and delivery.