← Back to library

Give Codex a research-folder instructions file

Mushtaq Bilal, PhD (@MushtaqBilalPhD) shows researchers using the Codex desktop app inside a project folder of papers, data and transcripts. An AGENTS.md written in plain English covers role, field standards, writing style and how to critique. Example tasks: screen papers against criteria, pull quotes from interviews, and rename PDFs after previewing the new names.

  • OutcomeOpen your research project folder in Codex, add a plain-language instructions file about role, standards, style and critique, and save every big result as a file.
  • SetupUnder an hour
  • LevelStarter
  • CreditMushtaq Bilal, PhD (@MushtaqBilalPhD)
View original
Works with
ChatGPTCustom agent

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You work from a folder of papers and data
  • You re-explain your project every session
  • You need repeatable screening

Not for: Confidential data you cannot share; Judgments about what counts as evidence

What do you need, and what do you get?

You need

  • Project folder
  • Instructions file
  • Screening criteria

You get

  • Screening tables
  • Extracted quotes
  • Saved result files

How does it work, step by step?

  1. Open the folderAdd your project folder as a Codex project.
  2. Write the instructionsDraft an AGENTS.md covering your role, field norms, preferred voice and how feedback should sound.
  3. Keep permissions onHave it ask before editing or deleting files.
  4. Run a tedious taskScreen papers or rename PDFs, previewing changes first.
  5. Save outputsAsk it to write each major result to a file.

The prompt

Our own prompt, inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD) and written to work in ChatGPT and Custom agent. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt6 variables
Create an AGENTS.md for my project in this folder with sections for Role ({my_field_and_project}), Standards ({citation_style_and_norms}), Voice ({style}) and Feedback ({focus}).
Then screen the PDFs here against {criteria} and save a table to {output_file} with a reason for each decision. Ask before changing any existing file.

Inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD): Codex 101 for Academic Researchers. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Scanned PDFs may be read poorly; check.
  • Do not put confidential details in the instructions file.
  • Stale instructions skew results; update them.

Our take

For nontechnical researchers, the instructions file is the high-leverage step. Writing down your field's standards, preferred citation style and how you want critique once turns a general assistant into a consistent collaborator for that project. Keeping file-change permissions on at first is wise while you learn what it does, and previewing rename lists before applying them avoids a mess in a folder you care about. Treat every screening pass as a first filter: you still decide inclusion, and you still read the papers that matter. Save outputs as files in the project so the work leaves a visible record rather than living only in chat. Be careful with interview transcripts and other human-subjects material; check your ethics approval and strip identifiers before any cloud tool sees them. For copyrighted PDFs, prefer tools that keep files on your machine, and follow your library's and publisher's rules. Start with one tedious task, such as renaming, before trusting it with analysis.

Where the time goes back: You stop re-explaining your project and can rerun screens consistently.

FAQ

Do I need to code?
The guide says no.
What stays with me?
The argument and judgments about evidence.

Source and credit

Inspired by Mushtaq Bilal, PhD (@MushtaqBilalPhD). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Codex 101 for Academic Researchers
Creator
Mushtaq Bilal, PhD (@MushtaqBilalPhD)
Published on
X
Original date
May 13, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pin your agent's write path with one contract test

Build a single fast test workflow that sends the same request key to your agent's booking or order write twice against a stand-in backend, then confirms from an append-only log that exactly one write happened, that the repeat ends as a deliberate skip, and that a forced timeout still lands as unknown and reaches a person, so refactors cannot quietly bring back duplicate writes.

Credit: ccch713

An afternoon+
Operations & AdminPrompt✓ AI dry run

Turn past AI corrections into a reusable instructions file

Ask the assistant that already knows your habits to draft a short handoff file from this chat and its memory of you, label every line as something you stated or something it inferred, attach a weak reply and a strong reply for the top three rules, combine drafts from a few strong chats, delete every inferred line you did not really teach, and store the finished file outside the chat so a new assistant can follow it.

Credit: u/Ok_Negotiation_2587 on r/ChatGPTPromptGenius

Minutes
Operations & AdminRoutine✓ AI dry run

Clear your inbox by voice while you walk

Talk through your email with a coding agent from your phone on a walk, and come back to drafts and a written to-do list.

Credit: Allie K. Miller (@alliekmiller)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Map and trim workflows before adding AI

Before building AI into a company, map each workflow with the people who do it, cut needless steps and plan the system, then add automation on top.

Credit: Luke Pierce (@lukepierceops)

An afternoon+