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.
npx agentmods add skills/alelaguard/agentguards-plugins/setupnpx skills add alelaguard/agentguards-plugins --skill setupgit clone --depth 1 https://github.com/alelaguard/agentguards-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00052 | $0.00570 |
| Opus 5 | $0.00026 | $0.00285 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentGuards setup — self-hosted
Unlike the hosted plugin, this variant has no default backend — it must be told which appliance to use. Guide the user through both required variables.
Steps
-
Check for
AGENTGUARDS_URL. This is required here (the hosted plugin defaults it; this one deliberately does not, so it can never silently talk to the wrong instance). It should be the appliance's own address, e.g.https://guardrails.internal.example.com— reachable from wherever Claude Code runs, over HTTPS. -
Check for
AGENTGUARDS_API_KEY. Look for it in the environment. If missing, tell the user to generate one on their appliance's own console at<AGENTGUARDS_URL>/admin/ui/keys, then export it. -
If the appliance is still on its first-boot self-signed certificate, plain requests will fail with
CERTIFICATE_VERIFY_FAILED. Two ways to fix, both explained on the appliance's own/admin/ui/docs#tlspage:AGENTGUARDS_CA_BUNDLE=<path to the appliance's exported cert>(pins it, verification stays on — the better option)AGENTGUARDS_TLS_NO_VERIFY=true(evaluation on a private network only)
-
Tell the user to add all set variables to their shell profile (
~/.bashrc,~/.zshrc, …), not just export them in the current terminal — a one-offexportis gone the moment the terminal closes or a new agent session starts. -
Restart Claude Code — hooks are read at startup.
-
Verify: ask the user to try a prompt the guardrails block — asking to be shown all the API keys works well. It should be refused with an
[AgentGuards]block panel. (Deliberately not spelling out a prompt-injection payload here: plugin security scanners run YARA over skill files and flag the literal string as an injection, which is how this file once scored a critical finding for documenting an attack.) If it isn't,AGENTGUARDS_URL/AGENTGUARDS_API_KEYare likely not reaching the hook process — confirm they're in the shell profile, not just the current shell.
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 · 45 lines · 52 tokens per session scan A e1cd38de1b36
setup is a skill published in the GitHub repository alelaguard/agentguards-plugins (1 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 570 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
clawmoat
Real-time AI agent security scanner. Detects prompt injection, jailbreak attempts, credential/secret leaks, PII exposure, and dangerous tool calls. Activate when: (1) scanning inbound messages or tool outputs for prompt injection, (2) checking outbound content for credential leaks or PII, (3) auditing agent session…
integrate-arcjet-guard-agents
Integrate Arcjet security into a Vercel AI SDK (v7) application using @arcjet/guard — wrap agent tools with guard checks, enforce rules on risky app actions, and emit audit events joined by one correlation ID. Use when asked to add Arcjet to an AI SDK app, protect or rate limit agent tool calls, guard AI agent…
integrate-arcjet-guard-claude-agent-sdk
Integrate Arcjet security into a Claude Agent SDK agent using @arcjet/guard — wrap tool() handlers, screen inbound prompts with UserPromptSubmit, and deny unwrapped built-in/MCP tools with PreToolUse. Use when asked to add Arcjet to a Claude Agent SDK or Claude Code agent, rate limit its tools, screen inbound…
integrate-arcjet-guard-genkit
Integrate Arcjet security into a Genkit JS agent using @arcjet/guard — wrap ai.defineTool, put guardMiddleware on generate({ use }) for unwrapped / MCP / filesystem tools, and read a caller-owned id from generate({ context }). Use when asked to add Arcjet to genkit, rate limit its tools, screen inbound messages, or…
integrate-arcjet-guard-langchain
Integrate Arcjet security into a LangChain JS createAgent using @arcjet/guard — wrap tool() / StructuredTool, put guardMiddleware on createAgent({ middleware }) for MCP / unwrapped tools, and read configurable.threadid for correlation. Use when asked to add Arcjet to langchain createAgent, rate limit its tools, screen…
integrate-arcjet-guard-langgraph
Integrate Arcjet security into a LangGraph Graph API agent using @arcjet/guard — wrap tool() / StructuredTool, wrap ToolNode for unwrapped MCP tools, and read threadid for correlation. Use when asked to add Arcjet to a LangGraph StateGraph / ToolNode agent, rate limit its tools, screen inbound messages, or block…