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 agents/jasonwarrenuk/goblin-mode/session-orchestratorgit clone --depth 1 https://github.com/JasonWarrenUK/goblin-modeWrote 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/agents/jasonwarrenuk/goblin-mode/session-orchestrator)<a href="https://agentmods.dev/agents/jasonwarrenuk/goblin-mode/session-orchestrator"><img src="https://agentmods.dev/badge/agents/jasonwarrenuk/goblin-mode/session-orchestrator.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.00089 | $0.00984 |
| Opus 5 | $0.00044 | $0.00492 |
| Sonnet 5 | $0.00018 | $0.00197 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
session-orchestrator 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 101 lines · 89 tokens per session scan A f666b4032a0e
session-orchestrator is an agent published in the GitHub repository JasonWarrenUK/goblin-mode (5 stars, last pushed 9d ago), with no licence file. It adds 89 tokens to every session and 984 once invoked, about $0.0004 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-31.
Other agents, from other repositories
do-pattern-implementer
Autonomous production pattern implementer for Durable Objects. Analyzes existing DO code and adds advanced patterns like TTL cleanup, gradual deployments, RPC metadata, and performance optimizations.
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
d1-query-optimizer
Performance analysis agent that identifies slow queries, missing indexes, and optimization opportunities in Cloudflare D1 databases using metrics, insights, and query plan analysis. Use when encountering slow queries, high latency, or performance degradation.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
optimization-agent
This agent should be used when the user asks to "optimize images", "improve image performance", "reduce image size", "choose image format", "configure image variants", "implement responsive images", or needs performance optimization strategies for Cloudflare Images.
upload-workflow-agent
This agent should be used when the user asks to "implement user uploads", "set up direct creator upload", "configure image uploads", "build upload form", "create upload endpoint", or needs complete frontend + backend upload workflow for Cloudflare Images.