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.
/plugin marketplace add charliechenye/SkillGatenpx agentmods add plugins/charliechenye/skillgate/17-public-pattern-agent-skill-plugingit clone --depth 1 https://github.com/charliechenye/SkillGateWrote 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/charliechenye/skillgate/17-public-pattern-agent-skill-plugin)<a href="https://agentmods.dev/plugins/charliechenye/skillgate/17-public-pattern-agent-skill-plugin"><img src="https://agentmods.dev/badge/plugins/charliechenye/skillgate/17-public-pattern-agent-skill-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
safe-example-plugin 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 3d 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": "safe-example-plugin",
"description": "Reduced plugin manifest for fixture coverage.",
"author": {
"name": "Example"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 15 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.
- 3d ago First seen · 8 lines scan A 20384b33cb14
safe-example-plugin is a plugin published in the GitHub repository charliechenye/SkillGate (2 stars, last pushed 15d 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-31.
Other plugins, from other repositories
claude-code-plugin
Install and manage the local-first HOL Guard package for Claude Code. This plugin guides setup and status checks; HOL Guard itself installs and owns runtime security hooks for risky commands, secrets, packages, MCP, and supply-chain activity.
claude-plugin-good
Example Claude plugin package.
trustabl
Self-audit AI agent, tool, and MCP-server code for security and reliability misconfigurations with Trustabl, the agent reliability scanner for the OpenAI Agents SDK, Claude Agent SDK, Google ADK, and MCP. Ships two skills (trustabl-scan and trustabl-enrich) and a subagent (trustabl) that together form a scan → enrich…
reins
Runtime security for AI agents. Blocks destructive actions before execution, routes high-risk operations through human approval, and maintains an immutable audit trail. Covers OWASP MCP Top 10, ASI Top 10, and Agentic Skills Top 10.
reins
Security controls for AI agents — deterministic policy enforcement, OWASP ASI10 scanning, and audit trails.
repo-forensics
Offline security scanner for AI-agent repos, skills, plugins, and MCP servers.