Borrowing it
Nothing to install: this file belongs to bdfinst/agentic-dev-team. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bdfinst/agentic-dev-team/main/.claude/skills/cloud-setup/SKILL.mdgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/cloud-setup)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/cloud-setup"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/cloud-setup/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/bdfinst/agentic-dev-team/cloud-setup"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/cloud-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 36 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00746 |
| Opus 5.5 | $0.00028 | $0.00298 |
| Sonnet 5.5 | $0.00014 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
cloud-setup 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.
What it actually says
Cloud sessions (claude.ai/code)
Plugins are a local CLI / IDE feature. A Claude Code web session runs in a fresh managed VM that clones this repo; setup scripts and env vars are set in the cloud UI (not a repo file) — see Claude Code on the web.
Install the plugin via the Setup script (loads this session). Claude
loads all skills, agents, and commands once when it starts, so the plugin must
be on disk before Claude launches. The environment Setup script (cloud UI) runs
pre-boot and its filesystem is snapshotted and reused — installing the plugin
there makes it load in the same session. The claude CLI is available in
cloud environments. Paste the body of .claude/cloud-setup.sh
into the Setup script field; it installs the toolchain and then the plugin
(claude plugin marketplace add bdfinst/agentic-dev-team +
claude plugin install dev-team@bfinster), always exiting 0. See
docs/cloud-setup.md for the focused recipe, the exact
snippet, and the verification probe.
SessionStart hook is a fallback only — it lands next session.
.claude/settings.json registers a SessionStart hook
(.claude/install-dev-team.sh), gated to DEV_TEAM_CLOUD_INSTALL=1 (set it
in Environment variables; leave it unset locally). Because the hook runs after
boot, the plugin it installs only takes effect on the next session — use the
Setup script for same-session loading.
If a network policy blocks the install, use the plugin's files directly. The skills and agents are plain files in this repo; run any workflow manually:
- a skill →
plugins/dev-team/skills/<name>/SKILL.md(e.g./plan→ readplugins/dev-team/skills/plan/SKILL.mdand follow its steps); - a review agent →
plugins/dev-team/agents/<name>.md; - the catalog →
plugins/dev-team/knowledge/agent-registry.md.
Test tooling in cloud. The same .claude/cloud-setup.sh that installs the
plugin also installs this repo's gates (jq, shellcheck, the Python
dev deps, and gh) — one paste into the Setup script field covers both. There
is no dedicated secrets store yet — treat env vars as visible to anyone who can
edit the environment.
For the full walkthrough of running a plugin's skills from a web session (the
Setup-script install plus the file-based fallback), see
docs/cloud-setup.md and
docs/using-plugin-skills-in-the-web-environment.md.
See plugins/dev-team/CLAUDE.md for the full orchestration pipeline configuration.
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 · 52 lines · 70 tokens per session scan A b1b1273b638b
cloud-setup is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 746 once invoked, about $0.0003 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 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 generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
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…
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".