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 skills add Threat-Vector-Security/guardian-agent --skill cloud-operationsgit clone --depth 1 https://github.com/Threat-Vector-Security/guardian-agentWrote 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/threat-vector-security/guardian-agent/cloud-operations)<a href="https://agentmods.dev/skills/threat-vector-security/guardian-agent/cloud-operations"><img src="https://agentmods.dev/badge/skills/threat-vector-security/guardian-agent/cloud-operations/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/threat-vector-security/guardian-agent/cloud-operations"><img src="https://agentmods.dev/badge/skills/threat-vector-security/guardian-agent/cloud-operations.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00543 |
| Opus 5.5 | $0.00000 | $0.00217 |
| Sonnet 5.5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
cloud-operations 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Operations
Use the built-in cloud and hosting tools for inspection and approved operations across Vercel, Cloudflare, Supabase, Fly.io, AWS, GCP, Azure, cPanel, and WHM.
Core Rules
- Check
<tool-context>for configured cloud profiles before asking the user to repeat provider details. - Prefer the narrowest read-only status or inventory tool first.
- Separate confirmed tool output from your inference.
- If the exact provider tool is not visible, call
find_toolswith the provider name before saying a capability is missing. - For Supabase and Fly.io, use
supabase_api/fly_apifor Management/Machines API operations andsupabase_cli/fly_cliwhen the provider CLI is the right surface. Mutating operations go through normal Guardian approval.
Provider Workflow
- Start with the provider health or account summary.
vercel_status,cf_status,supabase_status,fly_status,aws_status,gcp_status,azure_status,cpanel_account,whm_status
- Move to the narrow provider-specific tool that matches the request.
- Vercel: projects, deployments, domains, env, logs
- Cloudflare: DNS, SSL, cache
- Supabase:
supabase_apiorsupabase_cli - Fly.io:
fly_apiorfly_cli - AWS: EC2, security groups, S3, Route53, Lambda, CloudWatch, RDS, IAM, costs
- GCP: Compute, Cloud Run, Storage, DNS, logs
- Azure: VMs, App Service, Storage, DNS, Monitor
- cPanel / WHM: domains, DNS, SSL, backups, services, accounts
- Summarize the result in operator language.
- what exists
- what is degraded or unusual
- what the likely next inspection step is
Monitoring Guidance
- For recurring cloud checks, pair this skill with
automation-builder. - Prefer low-noise inventory or status checks before logs-heavy workflows.
- For possible security issues, hand off to
security-triageafter gathering the minimal cloud evidence.
Gotchas
- Do not jump straight to logs when a status or inventory tool can answer the question faster.
- Do not treat a missing configured profile as proof that the provider is unsupported; check
<tool-context>andfind_toolsfirst. - Do not hand-write provider-specific workflows if the provider CLI already owns the operation; run the CLI with explicit args instead.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 42 lines · 0 tokens per session scan A 34a697243695
cloud-operations is a skill published in the GitHub repository Threat-Vector-Security/guardian-agent (13 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 543 tokens. 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-30.
Other skills, from other repositories
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
analyzing-powershell-script-block-logging
Parse Windows PowerShell Script Block Logs (Event ID 4104) from EVTX files to detect obfuscated commands, encoded payloads, and living-off-the-land techniques. Uses python-evtx to extract and reconstruct multi-block scripts, applies entropy analysis and pattern matching for Base64-encoded commands, Invoke-Expression…
intent-recognition
Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an…
n8n-cli
Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and workflowbuildercreatetasks silence rules. Load whenever any of these tags appear or after calling workflowbuildercreatetasks.