Home Gallery Standard Research Blog GitHub Twitter LinkedIn Community

reverse-api-engineer system prompt

Category: Coding agents. Audited against the AISPA standard.

What is in reverse-api-engineer's system prompt?

reverse-api-engineer's full system prompt: 1 version, 1,280 characters. 5 instructions flagged, worst on harm prevention & user safety.

The full text of 1 prompt is reproduced below, 1,280 characters in all, each read instruction by instruction against the eight AISPA dimensions. 5 instructions were flagged as working against the person on the other end, most of them on harm prevention & user safety.

1 Prompts on record
5 Flagged instructions
AI audit Audit source
D3 · Privacy & Data Protection D4 · Tool/Action Safety D5 · User Agency & Manipulation Prevention D6 · Unsafe Request Handling D7 · Harm Prevention & User Safety

reverse-api-engineer - src reverse api prompts auto system

1280 characters · 5 flagged

You are an autonomous AI agent that automates browsing and captures network traffic for reverse engineering. For this provider your integration surface is: **{browser_tool_label}.** **Core principle:** The generated scripts must work immediately with zero user effort. Hardcode all credentials, cookies, tokens, and session data you discover. No env vars, no config files, no manual setup required. If you observe a token refresh, cookie renewal, or login flow in the traffic, implement automatic re-authentication so the script doesn't go stale. **HTTP requests:** When making HTTP requests in generated code, prefer `httpcloak` to match browser TLS/HTTP2 fingerprints. If `httpcloak` cannot bypass protections, fall back to fetching through the browser via Playwright CDP. Only use full browser automation as a last resort. ## Code generation {codegen_instructions} ## Guidelines - Narrate your actions as you browse - Capture all necessary API calls before generating code - Test your generated code to verify it works - Screenshots must be under 1MB — prefer element-specific screenshots or use snapshots for structure ## Output files {output_files} Confirm the files were created and briefly summarize: APIs discovered, auth method, whether it works, any caveats.

Instructions flagged against the user

D3 · Privacy & Data Protection
“Hardcode all credentials, cookies, tokens, and session data you discover.”
The prompt explicitly instructs the agent to hardcode all credentials, cookies, tokens, and session data into generated scripts, and to capture and embed authentication material. This is a severe violation of data protection principles, as it encourages storing sensitive secrets in plaintext code with no security safeguards.
D3 · Privacy & Data Protection
“Hardcode all credentials, cookies, tokens, and session data you discover. No env vars, no config files, no manual setup required. If you observe a token refresh, cookie renewal, or login flow in the traffic, implement automatic re-authentication so the script doesn't go stale.”
The prompt explicitly instructs the agent to hardcode all credentials, cookies, tokens, and session data into generated scripts, and to capture and embed authentication material. This is a severe violation of data protection principles, as it encourages storing sensitive secrets in plaintext code with no security safeguards.
D4 · Tool/Action Safety
“You are an autonomous AI agent that automates browsing and captures network traffic for reverse engineering.”
The prompt instructs the agent to autonomously capture network traffic, reverse engineer APIs, hardcode credentials, and implement automatic re-authentication — all without any validation, user confirmation, or least-privilege considerations. It actively encourages bypassing security protections (TLS fingerprint matching to evade detection). This violates tool safety principles.
D6 · Unsafe Request Handling
“You are an autonomous AI agent that automates browsing and captures network traffic for reverse engineering.”
The prompt is fundamentally designed to facilitate reverse engineering of services, bypassing security protections, and credential harvesting. There are no guardrails, no refusal mechanisms, and no safety policies to prevent misuse against unauthorized targets. The entire purpose could facilitate unauthorized access to systems.
D4 · Tool/Action Safety
“**HTTP requests:** When making HTTP requests in generated code, prefer `httpcloak` to match browser TLS/HTTP2 fingerprints. If `httpcloak` cannot bypass protections, fall back to fetching through the browser via Playwright CDP.”
The prompt instructs the agent to autonomously capture network traffic, reverse engineer APIs, hardcode credentials, and implement automatic re-authentication — all without any validation, user confirmation, or least-privilege considerations. It actively encourages bypassing security protections (TLS fingerprint matching to evade detection). This violates tool safety principles.
D6 · Unsafe Request Handling
“**HTTP requests:** When making HTTP requests in generated code, prefer `httpcloak` to match browser TLS/HTTP2 fingerprints. If `httpcloak` cannot bypass protections, fall back to fetching through the browser via Playwright CDP.”
The prompt is fundamentally designed to facilitate reverse engineering of services, bypassing security protections, and credential harvesting. There are no guardrails, no refusal mechanisms, and no safety policies to prevent misuse against unauthorized targets. The entire purpose could facilitate unauthorized access to systems.
D5 · User Agency & Manipulation Prevention
“**Core principle:** The generated scripts must work immediately with zero user effort. Hardcode all credentials, cookies, tokens, and session data you discover.”
The prompt is designed for fully autonomous operation with 'zero user effort' and no user confirmation steps for consequential actions like credential extraction, API reverse engineering, and code generation. There is no mechanism for user review before sensitive actions are taken.
D5 · User Agency & Manipulation Prevention
“Hardcode all credentials, cookies, tokens, and session data you discover. No env vars, no config files, no manual setup required.”
The prompt is designed for fully autonomous operation with 'zero user effort' and no user confirmation steps for consequential actions like credential extraction, API reverse engineering, and code generation. There is no mechanism for user review before sensitive actions are taken.

3 more in the interactive gallery.

Questions about reverse-api-engineer's system prompt

Does reverse-api-engineer's system prompt contain instructions that work against the user?

Yes. 5 instructions in reverse-api-engineer's system prompt were flagged as working against the person the product is talking to, most of them under harm prevention & user safety. Each one is quoted in full on this page, with the AISPA dimension it was judged under.

How long is reverse-api-engineer's system prompt?

1,280 characters across 1 prompt on this page. For comparison, the median system prompt in this index runs about 5,400 characters, so length varies by more than two orders of magnitude between products.

How many versions of reverse-api-engineer's system prompt are on record?

1. Older releases are kept rather than replaced, so the wording of a given version stays readable after the product has moved on.

Where did this reverse-api-engineer system prompt come from?

It was collected from publicly available sources and is reproduced here for transparency research, unedited. This site does not extract prompts from products itself.

How was reverse-api-engineer's system prompt audited?

Against AISPA, an eight-dimension standard for how an instruction treats the person on the other end: identity transparency, truthfulness, privacy, tool safety, user agency, unsafe request handling, harm prevention and fairness. This audit was ai audit. The method is described in the paper behind the standard.

How this page was made

The prompt text above is reproduced verbatim from a public source. Every instruction in it was read against AISPA, an eight-dimension standard for whether an instruction serves or works against the person the product is talking to. The standard, the annotation method and the findings across 1,058 prompts are set out in the paper, and the full catalogue is available as structured data.

All prompts here were collected from publicly available sources and are reproduced for transparency research. Browse the coding agents category, the full gallery of 400+ products, or read the paper behind the AISPA standard.