DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to fill in a web form and confirm what the site received with Scout

Give Scout the form details and get back exactly what the site recorded.

Authorization notice. Scout is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn office or operations worker who must submit the same web form repeatedly and needs proof of what was entered.

The problemRe-keying the same details into a web form is repetitive, and nobody checks what the site actually stored.

The outcomeThe form is submitted and the answer states what the site showed as received, with a replay as evidence.

What you need first

  • Node 22 or later
  • An Outcrawl key from outcrawl.ai for the cloud browser (1,000 free credits every month, no card needed)
  • A model service that speaks the standard chat completions API, hosted or running on your own computer
  • Optional: a local browser via `npm i playwright-core && npx playwright install chromium` if you do not use the cloud

Steps

  1. Run npm i @outcrawl/scout in your project folder.
  2. Run export OUTCRAWL_API_KEY=your-outcrawl-key, then set SCOUT_BASE_URL, SCOUT_API_KEY and SCOUT_HANDS_MODEL.
  3. Save the README's example as task.ts and write your form task, with the exact values to enter.
  4. Run npx tsx task.ts.
  5. Read result.data and result.error, then open result.replayUrl to check the submission.

Prompt for your agent

Use the outcrawl/scout repo to build task.ts that fills in the form at <form URL> with <the field values> and reports exactly what the site shows as received. Print result.data, result.status and result.replayUrl. Verify that the status is completed and the replay shows the submitted values.

Caveat. Scout submits forms on real sites, so test on a sandbox or low-stakes form first, since a finished run cannot be undone by Scout.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page