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/pireel/pireel-agentWrote 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/pireel/pireel-agent/pireel-claude)<a href="https://agentmods.dev/plugins/pireel/pireel-agent/pireel-claude"><img src="https://agentmods.dev/badge/plugins/pireel/pireel-agent/pireel-claude/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/pireel/pireel-agent/pireel-claude"><img src="https://agentmods.dev/badge/plugins/pireel/pireel-agent/pireel-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pireel 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 17d 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": "pireel",
"author": {
"name": "Pireel",
"url": "https://pireel.com"
},
"repository": "https://github.com/pireel/pireel-agent",
"license": "Apache-2.0",
"keywords": [
"pireel",
"video",
"video-editing",
"talking-head",
"shorts",
"captions",
"subtitles",
"transcription",
"storyboard",
"motion-graphics",
"claude-code",
"mcp"
],
"version": "0.7.13",
"description": "Edit multi-source videos and create finished cuts in Pireel Studio from your AI agent.",
"homepage": "https://pireel.com",
"skills": "./skills/",
"mcpServers": {
"pireel": {
"type": "http",
"url": "https://pireel.com/api/studio/mcp",
"headers": {
"x-pireel-distribution": "plugin",
"x-pireel-host": "claude-code"
}
}
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 111 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.
- 17d ago First seen · 38 lines scan A 83ebf12430ab
pireel is a plugin published in the GitHub repository pireel/pireel-agent (12 stars, last pushed 18d ago), licensed Apache-2.0. 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-19.
Other plugins, from other repositories
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.
svix
Teaches AI agents to send and receive webhooks the way Svix's own engineers would.
bench-creator
Capture private, reproducible AI coding benchmark cases from real repository work.
skills-analytics
Track and analyze Claude Code skill usage with a local dashboard.
icons
Integrate Font Awesome's icons into your project.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.