- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/claude-codex-settings --skill derive-client -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/claude-codex-settings --skill derive-client -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/claude-codex-settings --skill derive-client -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/claude-codex-settings --skill derive-client -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/fcakyon/claude-codex-settings/tree/HEAD/plugins/agent-browser/skills/derive-clientDel publicador
Driving a browser is the right tool for the first visit and the wrong tool for the hundredth. This skill records a site's network traffic once while you use it, then turns the captured requests into a standalone client (script, CLI, or library) that talks to the site's internal API directly.
The recording alone contains everything needed: agent-browser embeds text response bodies (JSON/HTML/JS) in the HAR by default, so endpoint shapes can be studied offline after the browser is closed.
1. Record Start HAR capture, drive the flows you want in the client
2. Identify Find the real API endpoints among the noise
3. Extract Pull request shapes, response schemas, and auth material
4. Generate Write the client, one function per flow
5. Verify Call every endpoint for real before declaring done
agent-browser network har start # embeds text response bodies by default
# ... drive the site: search, open a detail page, paginate, etc. ...
agent-browser network har stop /tmp/site.har
--content all embeds binary bodies too (base64); --content none disables embedding. Per-body cap is 2 MB.While the session is still open, agent-browser network requests and network request <id> give the same data interactively — but only the HAR survives navigation and browser close, so prefer it for anything multi-page.
Query the HAR with jq:
# All JSON API calls: method, URL, status
jq -r '.log.entries[]
| select(.response.content.mimeType | test("json"))
| "\(.request.method) \(.response.status) \(.request.url)"' /tmp/site.har
Ignore analytics and infrastructure noise: telemetry endpoints (/collect, /track, /beacon, /log), third-party domains (google-analytics, segment, sentry, datadog, intercom, hotjar), and static assets. The real API is usually first-party, JSON, and correlates with the actions you performed.
# Full detail for one endpoint: request headers, POST body, response body
jq '.log.entries[] | select(.request.url | test("api/search"))
| {request: {method: .request.method, headers: .request.headers,
postData: .request.postData.text},
response: .response.content.text}' /tmp/site.har
.response.content.text — this is the real payload, use it to derive types.authorization, cookie, x-csrf-token, x-api-key, and site-specific x-* headers. Replay only the ones that matter — test by omission in step 5.agent-browser cookies get --json > cookies.json for the client to load at runtime. Never hardcode cookie values into generated source.search(query), getItem(id)), typed from the observed response bodies.user-agent, referer, or x-requested-with.Call every generated function against the live API and compare the response shape with the recording. Common failures:
Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a standalone client or CLI that calls the endpoints directly, with no browser needed after the fir
---name: derive-clientdescription: Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a…---# plugins/agent-browser/skills/derive-client/SKILL.mdResumen general
Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a standalone client or CLI that calls the endpoints directly, with no browser needed after the first recording. Use when asked to "derive a client", "build a CLI for <site>", "reverse engineer this site's API", "record network requests", "turn this site into an API", or when the same site will be automated repeatedly and direct HTTP calls would beat driving the browser every time.
Preguntas frecuentes
Descarga plugins/agent-browser/skills/derive-client/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/fcakyon/claude-codex-settings.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.