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 alelaguard/agentguards-pluginsnpx agentmods add plugins/alelaguard/agentguards-plugins/claudegit clone --depth 1 https://github.com/alelaguard/agentguards-pluginsGrade A, and why
agentguards-claude 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": "agentguards-claude",
"displayName": "AgentGuards",
"description": "LLM security guardrails for Claude Code — jailbreak detection, prompt-injection and web-content scanning, data-exfiltration blocking, and destructive-command authorization. Bundles the AgentGuards MCP server plus enforcing hooks.",
"version": "0.2.30",
"author": {
"name": "AgentGuards",
"email": "[email protected]",
"url": "https://agentguards.co"
},
"homepage": "https://agentguards.co",
"repository": "https://github.com/alelaguard/agentguards-plugins",
"license": "MIT",
"userConfig": {
"agentguards_api_key": {
"type": "string",
"title": "AgentGuards API key",
"description": "Optional fallback for the hooks when AGENTGUARDS_API_KEY is not already set. The easiest way to set your key is to run /agentguards:setup in an Agent Mode or Local Code session and let Claude save it for you. Note the Claude Desktop app never reads a shell profile, so an export will not reach it.",
"sensitive": true
}
}
}
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 First seen · 23 lines scan A 0ed86a5cc2a1
agentguards-claude is a plugin published in the GitHub repository alelaguard/agentguards-plugins (1 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-31.
Other plugins, from other repositories
security-agent-skills
Security-testing methodology as portable agent skills, spanning white-box bug hunting, AI-agent and LLM red-teaming, cloud identity and CI/CD trust, client-app trust surfaces across browser and editor extensions and Electron, wire-protocol and token trust across gRPC, WebSocket, and JWT, infrastructure-as-code and…
unboundcompute
Plugin marketplace listing 1 plugin: security-agent-skills.
trust-issues
Plugin marketplace listing 1 plugin: trust-issues.
trust-issues
Adversarial, attacker-minded security review of untrusted code before you install it. A read-only scanner plus a five-persona reasoning pass, ending in a GO / GO-WITH-MITIGATIONS / NO-GO verdict.
cordon
Deterministic layer between untrusted content and agent actions.
bridgeward
Skeptical-reading and prompt-injection defense for AI coding agents. Trust nothing. Ship safely.