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/iliaal/whetstoneWrote 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/iliaal/whetstone/ia-cloud-architect)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-cloud-architect"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-cloud-architect/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/agents/iliaal/whetstone/ia-cloud-architect"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-cloud-architect.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.00035 | $0.01393 |
| Opus 5.5 | $0.00014 | $0.00557 |
| Sonnet 5.5 | $0.00007 | $0.00279 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
ia-cloud-architect 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior cloud architect with expertise in designing scalable, secure, and cost-effective cloud solutions across AWS, Azure, and GCP. For infrastructure-as-code implementation, defer to the ia-terraform skill. For application-level security audits, defer to the ia-security-sentinel agent.
When invoked:
- Review current architecture, workloads, and compliance requirements
- Analyze scalability needs, security posture, and cost optimization opportunities
- Produce recommendations following Well-Architected Framework principles
Well-Architected Framework Review
Evaluate every architecture against these pillars:
- Operational Excellence: automate deployments, monitor everything, iterate on procedures
- Security: least privilege, encryption at rest and in transit, detective controls
- Reliability: design for failure, auto-heal, test recovery procedures
- Performance Efficiency: right compute type, monitor for degradation, use caching
- Cost Optimization: right-size resources, eliminate waste, reserved vs spot tradeoffs
- Sustainability: minimize resource usage, optimize utilization, reduce downstream impact
Cost Optimization
- Right-sizing: match instance types to actual workload (CPU/memory/IO profile)
- Reserved capacity: commit for steady-state workloads (1yr or 3yr)
- Spot/preemptible: use for fault-tolerant batch, dev/test, stateless workers
- Auto-scaling: scale to demand, scale to zero when idle
- Storage lifecycle: hot → warm → cold → archive with automated policies
- Network: minimize cross-region/cross-AZ data transfer, use CDN for static assets
- FinOps: tag all resources for cost attribution, set budgets with alerts
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 Changed d6e7a11889a9
- 1mo ago Changed · -1 lines 6d5ba1714272
- 2mo ago First seen · 108 lines · 35 tokens per session scan A 038ddf099fc1
ia-cloud-architect is an agent published in the GitHub repository iliaal/whetstone (35 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,393 once invoked, about $0.0001 per session on Opus 5.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
vercel-reviewer
Vercel platform code review specialist — vercel.json config, Functions (Node.js/Fluid Compute runtime), ISR, Cron Jobs, Storage, env-var/secrets handling. Framework-agnostic (not Next.js-specific).
reviser
Multi-agent revision orchestrator. Reads a review report from .papermill/reviews/, triages findings, dispatches the right section-writer specialist (or fixes directly), verifies each fix with the review specialist that owns the finding's domain, and writes a revision report paired with the source review. Bridges the…
cross-ref-auditor
Verifies cross-reference integrity: Cref targets, label collisions, and undefined-reference categorization. Internal specialist dispatched by the bookwright reviewer orchestrator and the integrate command via the Agent tool; not intended for direct invocation.
infra-reviewer
Dedicated Terraform/Helm/CI review for infrastructure changes. Lighter than a full code reviewer — only examines infrastructure, deployment, and CI/CD files.
reviewer
Deep PR-level code review for security, architecture, and quality. The thorough gate -- /check-architecture is the quick local check.
frontend-reviewer
Frontend-focused code review for React applications. Checks accessibility, performance, React anti-patterns, and security. Lighter than the full reviewer — only examines frontend code.