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 agentmods add skills/neverinfamous/memory-journal-mcp/agents-sdknpx skills add neverinfamous/memory-journal-mcp --skill agents-sdkgit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/agents-sdk)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/agents-sdk"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/agents-sdk.svg" alt="Measured on agentmods" 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.00095 | $0.02115 |
| Opus 5 | $0.00048 | $0.01058 |
| Sonnet 5 | $0.00019 | $0.00423 |
| Haiku 4.5 | $0.00010 | $0.00212 |
Grade A, and why
agents-sdk 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 5d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Agents SDK
STOP. Your knowledge of the Agents SDK may be outdated. Prefer retrieval over pre-training for any Agents SDK task.
Documentation
Fetch current docs from https://github.com/cloudflare/agents/tree/main/docs before implementing.
| Topic | Doc | Use for |
|---|---|---|
| Getting started | docs/getting-started.md |
First agent, project setup |
| State | docs/state.md |
setState, validateStateChange, persistence |
| Routing | docs/routing.md |
URL patterns, routeAgentRequest, basePath |
| Callable methods | docs/callable-methods.md |
@callable, RPC, streaming, timeouts |
| Scheduling | docs/scheduling.md |
schedule(), scheduleEvery(), cron |
| Workflows | docs/workflows.md |
AgentWorkflow, durable multi-step tasks |
| HTTP/WebSockets | docs/http-websockets.md |
Lifecycle hooks, hibernation |
docs/email.md |
Email routing, secure reply resolver | |
| MCP client | docs/mcp-client.md |
Connecting to MCP servers |
| MCP server | docs/mcp-servers.md |
Building MCP servers with McpAgent |
| Client SDK | docs/client-sdk.md |
useAgent, useAgentChat, React hooks |
| Human-in-the-loop | docs/human-in-the-loop.md |
Approval flows, pausing workflows |
| Resumable streaming | docs/resumable-streaming.md |
Stream recovery on disconnect |
Cloudflare docs: https://developers.cloudflare.com/agents/
Capabilities
The Agents SDK provides:
- Persistent state - SQLite-backed, auto-synced to clients
- Callable RPC -
@callable()methods invoked over WebSocket - Scheduling - One-time, recurring (
scheduleEvery), and cron tasks - Workflows - Durable multi-step background processing via
AgentWorkflow - MCP integration - Connect to MCP servers or build your own with
McpAgent - Email handling - Receive and reply to emails with secure routing
- Streaming chat -
AIChatAgentwith resumable streams - React hooks -
useAgent,useAgentChatfor client apps
What ships with it
16 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.
- references/callable.md 2.2 KB
- references/codemode.md 5.4 KB
- references/email.md 3.4 KB
- references/mcp.md 3.5 KB
- references/mcp/code-mode-reference.md 16 KB
- references/mcp/oauth-reference.md 20 KB
- references/mcp/references/architecture-reference.md 15 KB
- references/mcp/references/cloudflare-quickstart.md 3.7 KB
- references/mcp/references/error-handling.md 19 KB
- references/mcp/references/http-security.md 10 KB
- references/mcp/references/implementation-guide.md 42 KB
- references/mcp/references/testing-reference.md 13 KB
- references/mcp/SKILL.md 3.2 KB
- references/state-scheduling.md 3.8 KB
- references/streaming-chat.md 4.1 KB
- references/workflows.md 3.9 KB
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.
- 5d ago First seen · 221 lines · 95 tokens per session scan A 4c8bd9d0f181
agents-sdk is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 2,115 once invoked, about $0.0005 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
maintain-splash-pages
The Lossless Group's pattern for repo-level splash pages — small Astro sites at /splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy…
system-audit
Periodic evidence-based self-audit of the whole agent system — the orchestrator, its docs/SSOTs, rules, memory, subagents, tools, infra and the work it claims to have delivered — followed by immediate cheap-safe fixes and a ranked backlog. Use when the user says 'аудит системы', 'проверь себя', 'самопроверка', 'system…
run-orchestrator
Execute 5-phase TDD workflow for complex features. Use when the user invokes /run, asks to build/create/implement a feature, requests a complex multi-file change, or types 'fasttrack:'. Enforces phase gates, sprint contracts, and builder!=reviewer discipline.
tech-writing
Write professional technical documents — requirements/PRD, tech spec/design doc, low-level design, decision records, and trade-off analysis — at a formality tier matched to the task. Grounds every claim in real code or a cited source, marks what it could not verify, and refuses to pad. Use when asked to write/update a…
plan-orchestrator
Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb…
perf-profiling
Systematic performance profiling and optimization across frontend (Core Web Vitals, code splitting, lazy loading), backend (N+1 queries, async), and database (EXPLAIN ANALYZE, indexing) layers. Use when the user reports slow code, latency, memory leaks, needs to benchmark, or wants to speed up an application. Measure…