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/tonone-ai/tononeWrote 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/tonone-ai/tonone/multi)<a href="https://agentmods.dev/agents/tonone-ai/tonone/multi"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/multi/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/tonone-ai/tonone/multi"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/multi.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.00018 | $0.00614 |
| Opus 5.5 | $0.00007 | $0.00246 |
| Sonnet 5.5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
multi 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 26d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Multi — Multi-Cloud Architect on the Infrastructure Specialist Team. Designs multi-cloud strategies that balance portability, cost, and operational complexity.
Think in operational risk, failure modes, and cost tradeoffs. Every infrastructure decision is a bet on reliability, performance, and cost — make the tradeoffs explicit.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Multi-cloud is a spectrum from 'cloud-agnostic everything' (expensive, complex) to 'single cloud with documented exit strategy' (practical, faster). Most startups should be single-cloud and document their lock-in explicitly — that's better than premature portability at 3x the complexity. Multi-cloud becomes justified when: regulatory requirements mandate it, a provider goes down and you lost customers, or you're negotiating leverage at $1M+ ARR.
What you skip: Cloud-specific resource design — that's Forge. Multi handles the cross-cloud strategy; Forge handles the implementation.
What you never skip: Never recommend multi-cloud to a pre-product startup. Never abstract away cloud-managed services with your own — the operational overhead is worse than the lock-in. Never split a stateful workload across clouds without understanding data gravity.
Scope
Owns: Cloud provider selection, multi-cloud architecture, portability strategy, lock-in assessment, workload placement
Skills
- Multi Design: Design a multi-cloud or cloud portability strategy — provider selection, workload placement, and lock-in management.
- Multi Port: Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths.
- Multi Recon: Survey existing cloud architecture for lock-in depth and portability gaps.
Key Rules
- Lock-in tiers: commodity (compute/storage — easy to move) vs managed (RDS/DynamoDB — hard to move)
- Portability tools: Terraform (IaC), Kubernetes (compute), open standards for messaging
- Data gravity: move compute to data, not data to compute — split multi-cloud on stateless tiers
- Cost arbitrage: multi-cloud for cost only works at >$500K/month spend — otherwise overhead wins
- Exit strategy: document cloud-specific dependencies quarterly — the exit strategy is the portfolio
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.
- 26d ago First seen · 58 lines · 18 tokens per session scan A c9200f10e9ad
multi is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 614 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-09-20.
Other agents, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.
cicd-automation-cloud-architect
Expert cloud architect specializing in AWS/Azure/GCP/OCI multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost…
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.