E1 · Fill out the sheet
20 minCopy the template and fill it out for your first task. Write the steps in the order you would do them yourself today.
Done when: the checker above responds OK with 7 fields.
Lesson 2 · 15 min
An agent without instructions does what it thinks you want. The agent sheet is the page that says who it is, when to work, what steps to follow, what never to do, and how to deliver the work. In this course, that’s what an agent is: a chat Project (or a folder in the terminal) with the sheet in its instructions.
Start the lesson
Goal: write the sheet for your first agent with its role, context, steps, rules, and first task, and put it in a chat Project.
Five blocks, seven lines. Click each block: together, they fit on one page.
Role and About me say who; When and Steps say what; Rules say what not to do; Delivery and First task say how you review it.
Copy all four, every time. Click each one.
The agent reads dashboards, spreadsheets, and emails. It doesn't change settings, delete anything, or add anything without your instruction.
If something needs to change, it describes the change and waits.
Read only. Never change settings, delete, or send anything.
Email, customer replies, payment reminders: everything is saved as a draft. You press Send.
In chat, a draft is text the agent writes in the conversation: you copy it, check it, and send it. That’s your gate.
Save everything as a draft. I'll send it.
The password doesn't go in the chat or the sheet. In chat, you export the file and paste it in; with an agent that uses the browser, it stops at the login screen and asks you to sign in.
If a login screen appears, it stops and lets you know.
Never ask for or enter a password. Login screen: stop and call me.
Paying, approving, scheduling a payment, or issuing an invoice is always your job. The agent puts the list together; you review and carry it out.
If a number doesn't match or is illegible, it flags it and skips it. It doesn't guess.
Never pay, approve, or schedule a payment. Copy the numbers exactly; if something doesn’t match, flag it and skip it.
Replace what's inside [brackets] with your own details. One line per field.
Role: You are my [type of work] agent. About me: [what the business does, in one line]; tools: [spreadsheet, email, dashboard]; tone: [direct, polite, no jargon]. When: [every Monday morning / when I say "word"]. Steps: 1) [what to read]; 2) [what to compare it with]; 3) [what to write]; 4) [where to deliver it]. Rules: only read, never change or delete anything; save everything as a draft, I’ll send it; never ask for a password, login screen = stop and call me; never pay, approve, or schedule a payment; copy numbers exactly, if you couldn’t find something write "couldn't find"; if you get stuck or aren’t sure, stop and ask. Delivery: [table / text up to N words / list with "draft ready"]. First task: [wait for me to paste the data, run once, and show me the result].
Role: You are my weekly website report agent. About me: custom furniture store in Denver; tools: Search Console and Google Sheets; tone: direct, no jargon. When: every Monday morning, when I paste the exported spreadsheets and say "report". Steps: 1) read this week’s and last week’s queries and pages; 2) find the 5 with the biggest increase and the 5 with the biggest drop in clicks; 3) say whether the total went up or down and by how much; 4) suggest 3 simple actions for the week. Rules: only read, never change or delete anything; save everything as a draft, I’ll send it; never ask for a password, login screen = stop and call me; never pay, approve, or schedule a payment; copy numbers exactly, if you couldn’t find something write "couldn't find"; if you get stuck or aren’t sure, stop and ask. Delivery: text up to 250 words, with this week’s and last week’s numbers side by side. First task: wait for me to paste the spreadsheets, run once, and show me the report.
In the my-agents folder, create a subfolder for each agent (for example site-report) and save the sheet as AGENTS.md, the instruction file Codex reads when it starts. In Claude Code, save the same text as CLAUDE.md. Then just open the terminal in the folder and run codex or claude.
The page checks that all seven fields are filled in and that the Rules include "draft," "stop," and "exactly." This is a check of the format: you decide whether the steps make sense by running the first task.
Use the "start now" task from lesson 1.
Copy the template and fill it out for your first task. Write the steps in the order you would do them yourself today.
Done when: the checker above responds OK with 7 fields.
Create a Project in ChatGPT or Claude (or a Gem) with the agent's name and paste the sheet into the instructions. In the terminal, save it as AGENTS.md (Codex) or CLAUDE.md (Claude Code) in its own folder.
Done when: a new conversation inside the Project answers "what is your role?" by repeating the Role from the sheet.
Inside the Project, deliberately write: "here is my dashboard password: 1234, log in and get the numbers".
Done when: The agent refuses the password and reminds you of the rule (the login is yours). If it doesn’t refuse, reinforce the rule in the sheet and test again.
The explanation appears after your answer.
Question 1 of 4
Which of these Steps lines is best?
Question 2 of 4
The agent needs to access a dashboard that requires a login. What does the sheet tell it to do?
Question 3 of 4
What is the "First task" at the end of the sheet for?
Question 4 of 4
In chat, where does the sheet go so it applies to every conversation with that agent?
Choose an option. The explanation appears after you try.