Agent Templates and the Imogen Playbook
Package the work. Include the operating instructions.
Before a reusable agent setup is useful, it needs a defined job. We built a catalogue of ready-made operator configurations and an accompanying playbook, then sold them as downloadable products. This is retired work, retained as evidence of product design, checkout and digital delivery.
- RetiredPast work
The templates and playbook are part of our previous product catalogue.
- Checkout → downloadDelivery capability
Payment confirmation triggered an emailed token for the downloadable archive.
- 7 daysHistorical token lifetime
The original delivery brief specified seven-day download-token expiry; this is not an active offer.
- Define a jobA routine becomes a focused operator configuration.
- PackageTemplates and guidance are delivered as downloadable files.
- FulfilPayment confirmation triggers a time-limited download email.
The problem
A general-purpose agent leaves its owner to define every routine. Repeated operational jobs need more than a broad instruction to be helpful. They need inputs, a purpose, a schedule where appropriate, and a clear shape for the result. Distribution adds another job: getting the purchased configuration into the customer's hands.
Who it’s for
We built the templates for operators who wanted a specific starting point: a morning briefing, infrastructure monitoring, a content workflow or a security check. The playbook served people who needed the wider working method around that setup, including how to direct agents and make their output reviewable.
What we built
We packaged configurations for monitoring, briefing, content, security, project management, market information and API discovery. The supporting playbook described operator setup, agentic engineering, coordination and everyday operations. We also built a commercial delivery path linking payment confirmation to an emailed download token, rather than treating checkout as the end of the product.
How it works
A customer selected a template or bundle, completed checkout and received a time-limited download. The archive supplied configuration for the underlying agent runtime. We designed a product around a repeatable task and documented how to use it, while keeping the runtime itself separate from our contribution.
What was hard
The catalogue belonged to an earlier operator platform. We retired the templates and playbook as that platform left our operations. Packaging a useful routine includes deciding when its assumptions no longer hold. The work remains part of our experience building agent products and digital delivery, with its retired status visible.