AI Agent Hub
Back to plugins
🧰

dsh-web-recon

Web Tools Updated 2026.08.14

Run the following command in DeepSeek Harness:

dsh plugin install sherconan/dsh-web-recon

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install sherconan/dsh-web-recon inside DeepSeek Harness to install the plugin; the source repository is available at https://github.com/sherconan/dsh-web-recon

About this plugin

The usual way an agent works a web back-office is screenshot, locate button, click, screenshot again—dozens of screenshots per workflow, thousands of tokens each, a redesign wipes everything, and the next session repeats the two-hour grind. dsh-web-recon takes a different shortcut: beneath the buttons there is already an HTTP API, and beneath the pixels an accessibility tree, both of which are far cheaper and far more stable.

It does one thing well: a single reconnaissance pass over a single-page application, with no button clicked, extracts the system's real API endpoints, authentication scheme, and noteworthy controls into a durable JSON playbook. web_replay then calls those endpoints directly from inside a dedicated browser, letting the browser natively handle cookies, CSRF, and CORS. Credentials never pass through the plugin, never printed, never stored. State-changing requests (POST/PUT/PATCH/DELETE) are refused by default and require explicit user consent. A dedicated browser, an origin allow-list with timestamped audit, and summary-only output form the security boundary.

Built for anyone who operates the same web admin panel, reporting system, or internal tool on a recurring basis. Learn it once, follow the playbook every session after, instead of guessing at the screen again.

Use Cases

  • Operating the same web admin panel or reporting system repeatedly without re-learning the UI each time
  • Discovering hidden APIs behind a single-page application and calling endpoints directly
  • Turning a one-time manual reconnaissance into a reusable automation playbook

Best For

  • Developers or automation engineers who drive web back-offices with agents
  • Ops personnel working with internal web tools, ERPs, or CRMs
  • Teams looking to cut agent token spend and improve workflow stability