James Washington
writing about archive utils free game ideas replays
Technique

Template-only auto-replies as a prompt-injection defense

An auto-responder that never lets an AI read the incoming email can't be tricked by it.

Letting AI make calls, safely

how it works

Fixed templates keyed on metadata; no model ingests bodies.

Technique: A pattern or hard-won lesson, written down so it isn't learned twice.

The code for this one lives in a private repo. This page explains the idea so you can build your own.

emailprompt-injectionsecuritytechnique

related

  • Recruiter scan-and-reply (template-only) Automation Replies to new recruiter emails with a resume using fixed templates.
  • Two-layer inbox classifier (rules first, LLM judge second) Automation Automatically labels every incoming email as belonging to one of several businesses or a personal area, so every downstream tool sees the same answer.
  • Code-owns-workflow, models-supply-judgment outreach pipeline Automation A program that researches leads and writes draft sales emails for a person to approve, never sending anything itself.
  • Agent Scratchpad: a moderated GET-addressable commons for sandboxed LLM agents Note An idea for a public message board that locked-down AI agents could use to coordinate, built so the humans can always watch.
  • agent-merge: Jev-gated self-merge for agent branches Automation The one sanctioned way an AI may merge its own work: a script that reviews it first and refuses if it didn't show its work.
← everything I've built
© 2026 James Washington
github twitter rss