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 oborchers/fractional-cto --skill multi-account-from-day-onegit clone --depth 1 https://github.com/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/multi-account-from-day-one)<a href="https://agentmods.dev/skills/oborchers/fractional-cto/multi-account-from-day-one"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/multi-account-from-day-one/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/oborchers/fractional-cto/multi-account-from-day-one"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/multi-account-from-day-one.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.02169 |
| Opus 5 | $0.00035 | $0.01085 |
| Sonnet 5 | $0.00014 | $0.00434 |
| Haiku 4.5 | $0.00007 | $0.00217 |
Grade A, and why
multi-account-from-day-one 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 12d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Separate Accounts Before You Write a Single Resource
Running development and production in a single cloud account is the most common shortcut in early-stage infrastructure, and it is cheap to fix on day one -- one afternoon of work. Six months later, when production databases share IAM policies with developer sandboxes, when billing is an undifferentiated blob, and when a misconfigured dev deployment takes down prod, the fix becomes a full migration measured in weeks. Multi-account isolation is not a scale concern. It is a day-one concern.
Why Single-Account Fails
A single cloud account creates invisible couplings that compound over time:
| Problem | Single Account | Multi-Account |
|---|---|---|
| Blast radius | A dev IAM policy change can affect prod resources | Accounts are hard boundaries; dev cannot touch prod |
| Billing | All costs in one bucket; cost attribution requires tagging discipline | Per-account billing is automatic and unambiguous |
| Permissions | Everyone who can deploy to dev can potentially access prod secrets | Cross-account access requires explicit trust policies |
| Service quotas | Dev load tests consume prod quota | Each account has independent quotas |
| Compliance | Auditors must review everything; no clean scope boundary | Prod account is the audit scope; dev is excluded |
| Credential blast | One leaked key exposes everything | One leaked key exposes one environment |
The longer you wait, the worse each problem gets. Resources accumulate. IAM policies intertwine. Developers build tooling that assumes a single account. Every day you delay makes the eventual migration more expensive.
The Minimum Viable Account Structure
Start with six accounts or projects. This is the minimum that provides meaningful isolation:
Organization Root
├── Management Account -- SSO, billing, organization policies
│
├── Security OU -- (GCP: Folder, Azure: Management Group)
│ ├── security -- Centralized security services
│ └── log-archive -- Immutable, centralized audit logs
│
├── Sandbox OU
│ └── sandbox -- Unrestricted experimentation, no prod access
│
└── Workloads OU
├── dev -- Development workloads
└── prod -- Production workloads
What ships with it
2 files 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.
- 12d ago First seen · 192 lines · 70 tokens per session scan A fd9a1ddf08b5
multi-account-from-day-one is a skill published in the GitHub repository oborchers/fractional-cto (30 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 2,169 once invoked, about $0.0003 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 skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…