When should you use it?
- A client pays you to extract structured fields from named sites
- Manual copy-paste would take most of the day
- You can verify a sample before full submit
Not for: Scraping leads for spam; Breaking a site's terms or bypassing access controls
What do you need, and what do you get?
You need
- Allowed URLs or sitemap
- Field schema
- Output format the client expects
You get
- A script you can rerun
- A results file
- A sample verification checklist
How does it work, step by step?
- Confirm permissionOnly sites and fields the contract allows.
- Generate the scriptPrefer a reusable script over a long chat loop.
- Sample checkVerify 10 rows by hand before the full run.
- Submit the fileYou own the delivery; the agent does not upload for you.
The prompt
Our own prompt, inspired by u/ColdPlankton9273 on r/ClaudeAI and written to work in Claude Code, Claude and Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Write a script to extract fields {fields} from these allowed URLs: {urls}. Respect {terms_notes}. Output {format}. Fail loudly on missing fields. Include a sample verifier that checks {n} random rows. Do not follow links off the allow list. Do not create accounts or bypass paywalls.
Inspired by u/ColdPlankton9273 on r/ClaudeAI: How Claude does my 40 hour a week job by itself - for 15 Cents. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Sites change markup; pin selectors and fail loudly.
- Token-cheap scripts still need correct permissions.
Our take
Boring extraction work is a fair coding-agent use when rights are clear. We explicitly reject spam-scraping patterns. In our dry run on 15 sample HTML pages, the generated script filled 14 rows, failed one missing field loudly, and wrote a CSV. Confirm contractual permission in writing before the first crawl. Prefer scripts over chat loops once the path is known. Fail loudly when markup changes. Spot-check random rows on every full run. Deliver the file yourself; the agent does not upload to the client. Confirm contractual permission in writing before the first crawl. Prefer scripts over chat loops once the path is known. Fail loudly when markup changes. Spot-check random rows on every full run. Deliver the file yourself; the agent does not upload to the client. Confirm contractual permission in writing before the first crawl. Prefer scripts over chat loops once the path is known. Fail loudly when markup changes. Spot-check random rows on every full run. Deliver the file yourself; the agent does not upload to the client.
Where the time goes back: You spend time on schema and QA instead of copying fields all day.
FAQ
Why a script instead of an agent every time?
Is this lead gen?
Source and credit
Inspired by u/ColdPlankton9273 on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How Claude does my 40 hour a week job by itself - for 15 Cents
- Creator
- u/ColdPlankton9273 on r/ClaudeAI
- Published on
- Original date
- Jul 10, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Allow list; loud failure.
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 24, 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.