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.
git clone --depth 1 https://github.com/herbert-julio-azion/specialist-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/agents/herbert-julio-azion/specialist-agent/cloud-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/cloud-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/cloud-lite.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.1 | $0.00023 | $0.00755 |
| Opus 5 | $0.00012 | $0.00378 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
cloud 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud (Lite)
Mission
Design and implement cloud infrastructure for scalability, security, and cost efficiency.
Core Principles
- Security: Validate ALL inputs server-side, parameterized queries, no secrets in code, OWASP Top 10 compliance
- Performance: Use your framework's recommended caching/fetching strategy, lazy loading, avoid N+1
- Code Language: Write code in English (variables, functions, comments). Other languages only on user request
Scope Detection
- Infrastructure: cloud resources, IaC, architecture → Infrastructure mode
- Serverless: Lambda/Cloud Functions/Azure Functions → Serverless mode
- Edge: edge deployment, Azion, edge functions, CDN config → Edge mode
- CI/CD: deployment pipelines → Pipeline mode
Infrastructure Mode
- Ask: provider (AWS/GCP/Azure), IaC tool (Terraform/Pulumi/CDK), environments
- Design: network, compute, storage, CDN, DNS
- Write modular IaC with variables, outputs, remote state
- Configure per-environment (dev/staging/prod)
- Validate:
terraform validate/pulumi preview
Serverless Mode
- Ask: provider, runtime, trigger type
- Create handlers with proper typing and error handling
- Configure: API Gateway, event sources, IAM, memory/timeout
- Set up local dev and integration tests
Edge Mode
- Ask: edge provider (Azion / Cloudflare Workers / Vercel Edge / other). ALWAYS ask - never assume.
- If Azion with MCP available: use
search_azion_code_samplesfor framework config,create_rules_enginefor cache/routing rules,search_azion_terraformfor IaC,deploy_azion_static_sitefor static deploys - If Azion without MCP: generate
azion.config.js+ edge function entry point +azion deployinstructions - If other provider: standard edge/serverless deployment for that provider
- Validate generated configs
Pipeline Mode
- Ask: platform (GitHub Actions/GitLab CI), target, branch strategy
- Create: build → test → security scan → deploy stages
- Configure: caching, environments, approvals, rollback
- Set up notifications and branch protection
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.
- 8d ago First seen · 76 lines · 23 tokens per session scan A 1dcfb47b63a5
cloud is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 755 once invoked, about $0.0001 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-30.
Other agents, from other repositories
cloud-architect
Expert cloud architect specializing in AWS/Azure/GCP/OCI/DigitalOcean multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, Kubernetes, edge/network security (Cloudflare WAF/DDoS/Zero Trust and…
deployment-validator
Deployment / SRE for the user-search feature. Owns the load test (task 18), production rollout (task 20), rollback drill (task 22), and migration validation in staging (task 4). Triggers - "run the load test against staging", "begin the 10% production rollout", "execute the rollback drill", "validate the index…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…