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/statusnpx skills add alelaguard/agentguards-plugins --skill statusgit clone --depth 1 https://github.com/alelaguard/agentguards-pluginsWrote 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/skills/alelaguard/agentguards-plugins/status)<a href="https://agentmods.dev/skills/alelaguard/agentguards-plugins/status"><img src="https://agentmods.dev/badge/skills/alelaguard/agentguards-plugins/status.svg" alt="Measured on agentmods" height="20"></a>What 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.00039 | $0.00400 |
| Opus 5 | $0.00019 | $0.00200 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
status scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w '%{http_code}\n' "$AGENTGUARDS_URL/health" What it actually says
AgentGuards status — self-hosted
There is no health_check MCP tool in this variant (see the guardrails
skill for why). Check status directly instead:
-
Confirm both required variables are set in the environment:
AGENTGUARDS_URLandAGENTGUARDS_API_KEY. If either is missing, stop here and point the user at thesetupskill — the hooks fail closed ("Not configured") without them, which blocks every prompt. -
Check the appliance is reachable, using the actual configured value — never hardcode a URL:
curl -s -o /dev/null -w '%{http_code}\n' "$AGENTGUARDS_URL/health"200means the appliance is up. A connection failure or a certificate error means the hooks will fail closed too — see thesetupskill's TLS step. -
Confirm the key is accepted, not just present:
curl -s -o /dev/null -w '%{http_code}\n' "$AGENTGUARDS_URL/v1/guardrails/evaluate-input" \ -H "X-API-Key: $AGENTGUARDS_API_KEY" -H 'Content-Type: application/json' \ -d '{"text":"status check"}'200means it's accepted.401means the key is wrong or was revoked on the appliance's own Keys page. -
Report plainly: which of the two variables are set, the
/healthstatus code, and the evaluate-input status code. Do not speculate beyond what these three checks actually showed.
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 · 35 lines · 39 tokens per session scan A c7ed886c4273
status is a skill published in the GitHub repository alelaguard/agentguards-plugins (1 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 400 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-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…
integrate-arcjet-guard-mastra
Integrate Arcjet security into a Mastra agent using @arcjet/guard — wrap createTool execute, screen input/output with a Processor tripwire, and gate unwrapped MCP/workspace tools with hooks. Use when asked to add Arcjet to a Mastra agent, rate limit its tools, screen inbound messages, or block prompt injection / PII.
deps-skill
Mentions dependency install commands for inventory.