Cloudflare Agents is a framework for building persistent, stateful AI agents on Cloudflare Durable Objects, where each agent has its own state, storage, and lifecycle. Developers use it to create agents with real-time communication, scheduling, model calls, MCP, workflows, and other server-side capabilities. The catalogue entries provide agent, skill, MCP, and instruction components for this framework.
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/agents --skill release-notesgit clone --depth 1 https://github.com/cloudflare/agentsWrote 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/agents/release-notes)<a href="https://agentmods.dev/skills/cloudflare/agents/release-notes"><img src="https://agentmods.dev/badge/skills/cloudflare/agents/release-notes/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/agents/release-notes"><img src="https://agentmods.dev/badge/skills/cloudflare/agents/release-notes.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.00033 | $0.00231 |
| Opus 5.5 | $0.00013 | $0.00092 |
| Sonnet 5.5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
release-notes 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
Release Notes
Turn implementation details into user-facing release notes.
Process
- Identify the user-facing outcome.
- Group related implementation details into one bullet.
- Avoid internal file names unless the user asks for engineering notes.
- Keep the tone factual and concise.
When the user provides a rough list of changes, run
scripts/format-release-notes.ts with { "changes": [...] } to create a first
draft, then polish the wording for the user's audience. The TypeScript script
is function-style (export default run(input, ctx)) and demonstrates reading
references/style-guide.md from ctx.files.
Output format
Use this structure:
## Summary
- One to three bullets describing what changed.
## Notes
- Optional caveats, migration details, or follow-up work.
If the input is too vague, ask for the target audience and the release scope.
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.
- 1mo ago First seen · 38 lines · 33 tokens per session scan A ed89cfed62df
release-notes is a skill published in the GitHub repository cloudflare/agents (5,841 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 231 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-08-30.
Other skills, from other repositories
release-publish
Publish an approved Orchard release.
release-review
Review Orchard deployment manifests.
orchard-release
Check deployment evidence and recovery conditions.
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.