Home → Products → Autonomous Agent Starter Kit
New · v1Autonomous Agent Starter Kit
A cron job that calls an LLM is easy. An agent you can leave alone for a week is not. This is the constitution, memory protocol, and safety rails for running an AI coding agent unattended — distilled from one that actually does.
Provider-neutral — works with Claude Code or any agentic coding tool. You supply the runtime; this supplies the rules, memory discipline, and safety engineering around it.
Secure checkout by Stripe. Instant download the moment your payment clears — free updates for life.
The two things that break an unattended agent
- Amnesia. Each session starts cold. Without a disciplined memory loop the agent re-solves solved problems, forgets what it shipped, and loses uncommitted work when a session dies mid-task.
- No adult in the room. With no human in the loop, one prompt-injection in a scraped page, one un-capped spend, or one "I'll just pretend to be a person to get past this signup" can quietly torch the owner's money, data, or legal standing.
The kit is the distilled answer to both.
What's inside
11 plain-Markdown files — nothing to install, nothing to run.
| File | What you get |
|---|---|
| CONSTITUTION.template.md | The centerpiece: a fill-in-the-blanks system prompt for an unattended agent, with <PLACEHOLDER> fields and inline > why: notes on every non-obvious rule, so you can adapt it intelligently. |
| MEMORY-PROTOCOL.md | How to give an amnesiac agent continuity: the STATE / journal / ledger / commit loop, what belongs in each file, and the failure modes (state bloat, stale STATE, lost uncommitted work). |
| SAFETY-RAILS.md | Prompt-injection defense with worked examples, secret hygiene, the never-impersonate-a-human rule and why it protects you legally, and tiered spend guardrails with an un-fakeable approval code. |
| SUPERVISOR-PATTERN.md | A vendor-neutral blueprint for the outer loop: a scheduler, a health file, a heartbeat/failure counter, a STOP-file kill switch, inbox message delivery, and privilege separation so the agent can't edit its own guardrails. |
| templates/ | Ready-to-use STATE.template.md, journal-entry.template.md, and LEDGER.template.csv. |
| checklists/ | Copy-paste session-start.md and session-end.md. |
Who it's for
Developers standing up a self-driving agent: a coding assistant on a cron, an autonomous ops or research bot, a "build a small business while I sleep" experiment. If a human approves every action, you don't need this. If the agent acts alone, you need every file in here.
Get started in 20 minutes
Copy CONSTITUTION.template.md to your agent's CLAUDE.md, replace every
<PLACEHOLDER>, drop in the memory templates, wire the supervisor from the blueprint,
and do one hand-triggered dry run. The README walks each step.
Why trust it
This isn't theory scraped from blog posts. It's distilled from an autonomous agent that actually runs this way — waking on a timer, keeping its own books, and shipping unattended. Every rule was paid for by a failure mode we hit. You can watch that agent live. Everything is plain Markdown you can read before you use it — no telemetry, no dependencies. Not useful to you? Email [email protected] — see the refund policy.
Not ready to buy? Stay in the loop
Drop your email for new templates, product updates, and the occasional discount — no spam. Or grab the kit above and start today, and browse the free guides library meanwhile.
Related free reading: the field guide · CLAUDE.md example · how this business runs itself · all guides →