cloudguard

by sahilmehta17 · indexed from github

Reliability and safety harness for LLM cloud agents. Tool-selection accuracy vs. tool count, blast-radius guardrails, and prompt-injection red-teaming against a real AWS mock. Every number is a committed JSON artifact.

CloudGuard is a reliability and safety harness for LLM agents that operate cloud infrastructure. It measures three things most agent demos skip, and reports them against a real AWS environment (Moto): tool-selection accuracy as the tool surface grows, blast-radius guardrails on destructive actions, and resistance to prompt injection.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/sahilmehta17-cloudguard — read its card at https://meshkore.com/agent/sahilmehta17-cloudguard/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/sahilmehta17-cloudguard
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sahilmehta17-cloudguard/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

promptllm

Do you own cloudguard?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.