sendsets
AGENTS.md1 starsChanged 52 days agoApache-2.0View on GitHub
Sendsets is a cold email API for AI agents. Use it when a task involves sending cold or outbound email, running an email campaign or sequence, connecting or warming up a sending mailbox, adding leads to outreach, or reading and answering replies. Rules that protect the user's sender reputation:
- Installs packages
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- llms.txtllms.txt
- send-cold-emailSkill
- sendsets-cliSkill
- sendsetsSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 1 is common, 0 are distinctive, and 0 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 15
Never invent API keys, mailbox credentials, product endpoints or events.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sendsets for agents
Sendsets is a cold email API for AI agents. Use it when a task involves sending cold or outbound email, running an email campaign or sequence, connecting or warming up a sending mailbox, adding leads to outreach, or reading and answering replies.
- MCP server:
https://api.sendsetsapi.com/v1/mcp(streamable HTTP; OAuth 2.1 with dynamic client registration, orAuthorization: Bearer ssk_...) - Skill: read
skills/sendsets/SKILL.mdfirst; its references sit beside it and are read only when a step needs them - CLI:
brew install addisonhoff/tap/sendsets(Scoop on Windows, see README), thensendsets login --hostname sendsetsapi.comandsendsets doctor --json - REST API:
https://api.sendsetsapi.com/v1, spec at https://gist.githubusercontent.com/AddisonHoff/abfb01a48dc15edef07cb188cbb70d04/raw/openapi.json - Docs: https://docs.sendsetsapi.com/api/
Rules that protect the user's sender reputation:
- A test send and a campaign launch are separate decisions. Never launch a live campaign unless the user explicitly asked to send.
- Provisioning a managed mailbox is a recurring charge. Show the live quote first.
- Never invent API keys, mailbox credentials, product endpoints or events.
- Retry an identical write with the same
Idempotency-Key. - A send tool that answers
awaiting_approvalneeds a person to approve it in the dashboard; hand them theapproval_urland wait.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

