no-leaky-app
Installation
SKILL.md
no-leaky-app
Check the responses your app sends, not the code that is supposed to produce them. A header added in one route handler is missing from the 404 page, and a policy that looks strict can still allow inline scripts. Every claim carries a receipt: the response, its headers, and what changed. Work only on an app you own or are authorised to change.
1. Collect one of each response
Run the app and request one of each: a page, a 404, an error page, a static file, an API response that carries account data, and a redirect if there is one. Save the headers of each (curl -s -D - -o /dev/null URL). These are the before receipts.