Cloudflare Computer is a virtual filesystem whose state is stored in SQLite inside a Durable Object and exposed through selectable execution backends. It lets coding agents work with files, shell commands, JavaScript modules, containers, and networked Linux environments.
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 cloudflare/computer --skill gardenergit clone --depth 1 https://github.com/cloudflare/computerWrote 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/cloudflare/computer/gardener)<a href="https://agentmods.dev/skills/cloudflare/computer/gardener"><img src="https://agentmods.dev/badge/skills/cloudflare/computer/gardener/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/cloudflare/computer/gardener"><img src="https://agentmods.dev/badge/skills/cloudflare/computer/gardener.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.00047 | $0.03764 |
| Opus 5.5 | $0.00019 | $0.01506 |
| Sonnet 5.5 | $0.00009 | $0.00753 |
| Haiku 4.5 | $0.00005 | $0.00376 |
Grade A, and why
gardener-tasks 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 3d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gardener tasks
Gardener runs AI maintenance tasks on this repository from GitHub Actions. Each task is one Markdown file: YAML frontmatter says when it runs, what the model may read, and exactly which changes it may make; the body is the model's instructions. A planning job runs the model with only the declared tools and lets it propose only the declared effects. A separate job then applies those proposals. Nothing outside the declaration is possible, whatever the instructions say.
Files
.gardener/
gardener.json project settings (release pin, optional "handle"); edit only "handle"
gardener.lock.json generated; never edit
SKILL.md this file; generated
tasks/<dir>/TASK.md one task per directory; the only files you write
.github/workflows/
gardener-<id>.yml generated, one per task; never edit
gardener-sync.yml generated (or the "syncWorkflow" name in gardener.json); never edit
Workflow
- Create
.gardener/tasks/<dir>/TASK.md. Start from the template below or an existing task. - Run
npx @scuffi/[email protected] generatefrom the repository root (or the repository's ownpackage.jsonscript, if it has one). Use this exact version: a different one produces files the pull request's Check tasks check rejects. - Fix every error
generateprints and read its warnings. Repeat until it succeeds. - Commit the
TASK.md,.gardener/gardener.lock.jsonand the.github/workflows/gardener-*.ymlchanges together. When they reach the default branch, the sync workflow enables the task.
To change a task, edit its TASK.md and run generate again. To remove one, delete its
directory and run generate. Never hand-edit generated files.
Template
---
schema: gardener.task/v1
id: bug-intake
name: Bug intake
description: Asks issue authors for missing reproduction details.
trigger:
event: github.issue.opened
labels-all: [bug]
tools:
- repository.list_files
- repository.read_file
effects:
- issue.comment.create
network:
default: deny
allow: []
deny: []
limits:
runtime-seconds: 300
max-turns: 12
max-tool-calls: 16
input-tokens: 60000
output-tokens: 16000
---
Read the issue and the code it mentions. If it is missing reproduction steps, expected behaviour or
a version, propose one `issue.comment.create` asking for exactly what is missing. Otherwise
propose nothing. Then finish.
What ships with it
6 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.
- 3d ago Changed · +21 lines 6475dc1e77bd
- 7d ago Changed · +1 lines 602f83402761
- 9d ago Changed · +3 lines d4f8b5272a55
- 14d ago First seen · 241 lines · 47 tokens per session scan A 540f3539e937
gardener-tasks is a skill published in the GitHub repository cloudflare/computer (9,607 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 3,764 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.