Agent build · v1
AI outreach agent team: short-lived role agents on a schedule (free sample)
What it does: The layout of a Claude Code agent team that runs replies, inbox and numbers on a schedule. Each role wakes up, does one run, writes down what it learned, and exits. Sample of the paid kit.
- Model
- Claude Opus and Claude Sonnet (Claude Code background agents)
- Runs in
- Claude Code scheduled tasks, Playwright over CDP
- Cost per run
- not measured
- License
- MIT
- Used by
- 0
- Files
- 8 (20 KB)
curl -L https://tensorust.com/builds/ai-outreach-agent-team/download -o ai-outreach-agent-team.zip
Receipts
- Source
- https://agent-receipts-five.vercel.app/
- Measured
- Oct 22, 2026
- Check
- Number found on the source page by our checker
- Stamp
- w5H4zZScAptjReQTwOTdHqZ7ELh2hJd_
- Source
- https://agent-receipts-five.vercel.app/
- Measured
- Oct 22, 2026
- Check
- Number found on the source page by our checker
- Stamp
- N8LcJHO392fsJGWy_O4kp8pjF7_h1543
Files
- .claude/skills/agent-team-restart/SKILL.md2 KB
- README.md3 KB
- roles/numbers/ROLE.md2 KB
- roles/x-reply/ROLE.md3 KB
- schedule.example.json4 KB
- shared/LEARNING-LOOP.md1 KB
- shared/RULES.md3 KB
- tools/start-browsers.ps11 KB
# X REPLY (one run, then exit)
Job: find the best live threads for each account and post exactly one reply per account. Execution over output: if no line is genuinely strong, post nothing.
## Read first
- agents/README.md top headers (team rules)
- this file and NOTES.md (LESSONS block first)
- the top of VOICE.md
## Cadence (checked in posts.json before acting)
- One reply from the brand account and one from the personal account per run. Never more.
- Skip an account if it already replied in the last 50 minutes.
- Skip any handle that account replied to in the last 24 hours.
- The two accounts never reply to the same target or to each other.
## Steps
1. Get the time with `date`.
2. Find targets yourself with live X search, at most 6 searches, at least 60 seconds apart. Stop on the first 429.
3. Pick the 2 best threads written by real people (not brands or news accounts) in your lane. Prefer posts under 6 hours old with a large and growing view count, and threads that ask a question.
4. For each, find one verdict-changing fact that is newer than the thread, with a source URL you have opened.
5. Write the reply: the useful outcome or the fact in line 1, so a stranger gets it with the parent cropped off. 2 to 4 short lines. No academic citations, no links unless the thread asked for one.
6. Post the brand reply in the brand account's Chrome, after confirming the signed-in profile is the brand. Post the personal reply in the personal Chrome, after the same check.
7. While searching, add any strong article or explainer topic you see to the topic queue (one line, with the source URL).
## What the data said (our own measurements, keep testing)
- A line 1 that stands alone beat a line 1 that needs the news by about 8x on median views.
- Reversal and "everyone who..." shapes beat plain quips. Tips and advice as replies did worst.
- Replies under fresh, huge threads got hundreds of views; the same replies under old threads got single digits.
- When one of our replies takes off, answer the best 1 or 2 replies under it.
## Hard rules
- Product mentions only when the thread asks for exactly what we make, disclosed as ours ("made this one").
- No likes, no follows, no follow-for-follow.
- Never sign out, switch accounts or close tabs you did not open. Never type passwords or hunt for credentials.
## Log
- posts.json: platform (x-brand-reply or x-personal-reply), ts, url, target handle, text.
- NOTES.md: the exact lines, why you picked the target, and what you are testing.
- Finish with the exact lines posted and their URLs, or why you skipped.
README
This is the structure behind the agent team that has run Tensorust's distribution since 2026-10-09: X replies, long-form articles, cold email, an inbox closer and a daily numbers agent. It runs on Claude Code. Nothing stays on. A scheduled job wakes up, spawns one short-lived background agent for one role, the agent does one run, and it exits.
Each role is two files. ROLE.md is the playbook: the job, what to read first, the steps, hard caps and what to log. NOTES.md is the role's memory: a LESSONS block at the top that the agent reads before acting, and a run log it appends to after (TRIED, RESULT, LESSON). Shared files hold the voice, the goals, and posts.json, a log of every action with its live URL. Cadence limits are checked against posts.json before anything is posted, so two runs can never double-post.
What is in this sample:
README.md: the architecture and how a run works.
shared/RULES.md: the rules every role reads first (real Chrome only, never sign out, reuse tabs, stop on 401 and 429, log the live URL).
shared/LEARNING-LOOP.md: how roles get better between runs.
roles/x-reply/ROLE.md and roles/numbers/ROLE.md: two of the role briefs.
schedule.example.json: three jobs with their exact prompts, including the precheck the main session runs before spawning anything.
.claude/skills/agent-team-restart/SKILL.md: a skill that brings the whole team back in a fresh session.
tools/start-browsers.ps1: starts the Chrome profiles agents attach to.
How to run it:
1. Start Chrome profiles with remote debugging (tools/start-browsers.ps1) and sign into each account by hand.
2. Put the files under outreach/ as laid out in README.md, write your own VOICE.md and PLAYBOOK.md, and fill the handles and ports in schedule.json.
3. In Claude Code, run the restart skill. It checks logins read-only and creates one scheduled job per entry in schedule.json.
/agent-team-restartScheduled jobs in Claude Code live only in the session and expire after 7 days, so run the restart skill in every new session and at least weekly.
What to change: your platforms, your ports, your voice, and the cadences. Start with low cadences; new accounts get rate-limited fast. Keep the shape: one run per agent, cheap prechecks in the main session, every action logged with a live URL, and a numbers agent that writes one change per role per day.
The full kit, The Agent-Run Outreach Team, adds the other roles (scout, LinkedIn, community, articles, revenue), the pacing gate and posts log enforced in code, the scorecard and learning scripts, and a setup guide: https://shop.tensorust.com/