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 harness/harness-ai --skill manage-cdegit clone --depth 1 https://github.com/harness/harness-aiWrote 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/harness/harness-ai/manage-cde)<a href="https://agentmods.dev/skills/harness/harness-ai/manage-cde"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/manage-cde/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/harness/harness-ai/manage-cde"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/manage-cde.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.00111 | $0.01058 |
| Opus 5 | $0.00056 | $0.00529 |
| Sonnet 5 | $0.00022 | $0.00212 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
manage-cde 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 9d 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.
This is a copy
100% identical to manage-cde — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage CDE
Configure on-demand Cloud Development Environments with workspace templates, auto-hibernation, and cost controls in Harness.
Instructions
Step 1: Establish Scope
Confirm the user's org, project, team, and technology stack.
Call MCP tool: harness_list
Parameters:
resource_type: "project"
org_id: "<organization>"
Step 2: Identify the CDE Task
Determine which workflow the user needs:
- On-Demand Environment Setup -- Environment templates with resource allocation and lifecycle
- Workspace Standardization -- Pre-configured templates per team/stack with consistent tooling
Step 3: Configure On-Demand Environments
Gather from the user:
- Technology stack and runtime version
- Cloud provider (AWS, GCP, Azure)
- IDE preference (VS Code browser, VS Code SSH, JetBrains Gateway)
- Git provider for auto-clone on start
Design the environment template:
Resource allocation:
- Default size (e.g., 4 vCPU, 8GB RAM) with upgrade options
- Persistent storage for workspace files
- Ephemeral storage that clears on stop
Lifecycle configuration:
- Provisioning trigger: developer request, PR creation, or branch push
- Start time target (under 30 seconds recommended)
- Auto-stop after idle timeout (default 30 minutes)
- Persistent mode option for long-running work
Integrations:
- Secret injection from Harness Secrets, Vault, or cloud secret managers
- Supporting services (databases, caches, message queues) via Docker Compose or Kubernetes
- Custom access URL pattern (e.g., {user}-{env}.dev.company.com)
Cost controls:
- Daily cost cap per environment
- Team-level monthly budget
- Auto-hibernation for idle environments
Step 4: Create Workspace Templates
When standardizing across teams, create templates per role/stack:
Backend Service Developer:
- Runtime, build tools, testing frameworks
- Database clients, API testing tools
- Pre-configured debugger and linter
Frontend Developer:
- Node.js runtime, package manager
- Browser dev tools, component library
- Hot-reload and preview server
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.
- 9d ago First seen · 134 lines · 111 tokens per session scan A d788b35be072
manage-cde is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 18d ago), licensed Apache-2.0. It adds 111 tokens to every session and 1,058 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to manage-cde, differing in 0 lines, and is treated as a copy.
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-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…
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).
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…