What is shoot-email AGENTS.md?

A set of project instructions for building Shoot Email, a command-line email client and service. It describes a planned design using a local service and database with Cloudflare for sending, receiving, and routing email.

Use it when planning Shoot Email's command-line interface, local service, database, Cloudflare email setup, inbound email Worker, or future MCP integration.

It gives the coding agent the project's intended direction and architecture, reducing guesswork when planning or implementing the system.

How powersurge01/shoot-email configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to powersurge01/shoot-email. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/powersurge01/shoot-email/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/powersurge01/shoot-email

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/powersurge01/shoot-email/agents-md/github.svg)](https://agentmods.dev/instructions/powersurge01/shoot-email/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/powersurge01/shoot-email/agents-md"><img src="https://agentmods.dev/badge/instructions/powersurge01/shoot-email/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/powersurge01/shoot-email/agents-md"><img src="https://agentmods.dev/badge/instructions/powersurge01/shoot-email/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,723 This file is loaded in full into every session.

When invoked 3,723 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.03723	$0.03723
Opus 5.5	$0.01489	$0.01489
Sonnet 5.5	$0.00745	$0.00745
Haiku 4.5	$0.00372	$0.00372

Measured 2mo ago against content hash 3bf382e0d9e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

shoot-email AGENTS.md 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 2mo 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.

AGENTS.md · 402 lines

How it starts

The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Shoot Email CLI Planning Notes

Product Direction

Build a terminal-first email client/service that lets users send text emails and check received text emails from the command line. Start with a CLI because it is easy to build, inspect, and debug. Later, wrap the same service layer in an MCP server and use it as the backend for a ChatGPT app.

Recommended Architecture

CLI
  -> local API/service
    -> local database
    -> Cloudflare Email Sending API

Cloudflare Email Routing
  -> Email Worker email() handler
    -> parse inbound email
    -> POST normalized JSON to backend webhook
    -> validate/store message
    -> CLI reads messages from database

The CLI should be the user interface, but it should not be the whole system. Receiving mail requires Cloudflare Email Routing plus a Worker email handler. The Worker parses inbound mail and posts normalized JSON to the backend webhook.

Cloudflare Fit

Cloudflare Email Service is the preferred provider because it supports:

Receiving inbound mail through Email Routing.
Running custom inbound logic through an Email Worker.
Sending outbound mail through Email Sending.
Keeping DNS, inbound routing, outbound sending, and edge logic on one platform.

For development, use wrangler dev to test Email Routing behavior locally. When a deployed Worker needs to reach a local backend, expose the local webhook with a tunnel such as cloudflared or ngrok until the service is moved to a small cloud host.

Hosting Decision

Host the durable HTTP backend on Cloudflare Workers Paid and use Neon Postgres with pgvector as the managed database. Connect the Worker to Neon through a Hyperdrive binding with query caching disabled initially. Worker requests use a request-scoped pg.Client; local CLI, migration, and integration-test paths continue using pooled Docker Postgres.

Use transaction-scoped lock rows with SELECT ... FOR UPDATE for outbound quota coordination. Do not use PostgreSQL advisory locks through Hyperdrive; they are not supported.

Read the full file on GitHub · 402 lines

Changes

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.

2mo ago First seen · 402 lines · 3,723 tokens per session scan A 3bf382e0d9e5

Subscribe to this mod's changes

shoot-email AGENTS.md is an instructions file published in the GitHub repository powersurge01/shoot-email (0 stars, last pushed 3mo ago), licensed MIT. It adds 3,723 tokens to every session, about $0.0149 per session on Opus 5.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.

LLM cloudflare-workers codex email mcp neon

shoot-email AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
shoot-email AGENTS.mdpowersurge01/shoot-email	Instructions file	0	3mo ago	MIT	A	3,723	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

shoot-email: Instructions file for Codex