💡 How to use these prompts:
Replace everything in [BRACKETS] with your specific details before sending.
Click Copy to copy any prompt to your clipboard instantly.
I want to run an agent in CI doing: [DESCRIBE THE TASK]
My workflow has access to: [LIST SECRETS, TOKENS, NETWORK ACCESS]
Tell me:
- Which of those the task genuinely needs
- What each unnecessary one would let a misbehaving agent do
- The narrowest set that still works
- What breaks if I remove each
Assume I would rather the job fail than overreach.
My CI agent will handle: [DESCRIBE]
Write the list of actions it must never take, regardless of what it concludes is correct.
Then tell me how each one would be enforced technically rather than by instruction, and which ones I cannot enforce that way.
The last group is the risk I am accepting.
My agent will open pull requests for: [DESCRIBE]
Tell me what limits to set on diff size, files touched and scope per run — and why each limit helps.
Research on agent pull requests found larger diffs merge less often. Use that as the starting assumption.
My CI agent runs unattended doing: [DESCRIBE]
Write what happens when it goes wrong:
- How I find out
- How I stop it mid-run
- What I check to see what it touched
- What I would need to roll back
If any step is I would not notice, say so.
My CI agent reads: [ISSUE TEXT, PR DESCRIPTIONS, COMMIT MESSAGES, EXTERNAL FILES - LIST WHAT APPLIES]
For each, tell me whether a third party can put text there, what they would try to make the agent do, and what in my setup would stop it.
Public repositories mean anyone can write an issue. Treat that as untrusted input.
I am considering running this in CI: [DESCRIBE]
Argue against it. What makes it worse unattended, what a person would catch, what happens if it runs at 3am on a Sunday, and whether the time saved justifies the exposure.
Then tell me whether your argument holds.