More screenshots
Works with the AI Agents you already use
HAR File Safety Check
In 2023, session tokens taken from HAR files uploaded to a vendor's support system were used to hijack customers' admin sessions.
$5
HAR File Safety Check
Example session with this skill installed
Check this project with har-file-safety-check.
- Read your context and instructions
- Compiled the har file safety
$ python3 scripts/check_har.py examples/risky
BLOCK support/checkout-bug.har:191 H04 SECRET_IN_REQUEST_BODY
entry 2 (shop.example.com): post data field password: value hidden
Why: Request post data (form fields, JSON, multipart, or a WebSocket message the page sent) holds a password, client secret, token, card number or JWT. HAR files keep request bodies as plain text, and sanitized exports remove only cookie and Authorization headers, so recording a login or payment step leaves the password or card number in the file.
Safer: Sign in before you start recording, or replace these values with REDACTED in postData.text and postData.params before sharing. Change a password that was captured.
BLOCK support/checkout-bug.har:205 H02 COOKIE_SAVED
BLOCK support/checkout-bug.har:223 H05 SECRET_IN_RESPONSE_BODY
BLOCK support/checkout-bug.har:293 H01 AUTH_HEADER_SAVED
BLOCK support/checkout-bug.har:297 H02 COOKIE_SAVED
BLOCK support/checkout-bug.har:380 H03 SECRET_IN_URL
REVIEW support/checkout-bug.har:21 H13 PERSONAL_DATA
REVIEW support/checkout-bug.har:40 H12 SHORT_LIVED_LOGIN_DATA
REVIEW support/checkout-bug.har:191 H13 PERSONAL_DATA
REVIEW support/checkout-bug.har:301 H11 API_KEY_OR_AUTH_HEADER
REVIEW tests/fixtures/stock-levels.har:18 H14 INTERNAL_HOST
REVIEW tests/fixtures/stock-levels.har:28 H11 API_KEY_OR_AUTH_HEADER
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 2 files, 2 with HAR content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A HAR exported "with sensitive data" holds the session cookie and Bearer token of the person who recorded it, and anyone who receives the file can open the site as that person without the password or the second factor. In 2023, session tokens taken from HAR files uploaded to a vendor's support system were used to hijack customers' admin sessions. This skill checks a HAR for ten kinds of sensitive data before you send or commit it, and tells you how to clean each one: export again sanitized, replace the values it names, and sign out so a copy that already went out stops working.
Your agent runs a scanner on your .har files (exports from Chrome, Edge, Firefox and Safari DevTools, Charles and Fiddler, and Playwright recordings used as test fixtures). It reads the HAR 1.2 structure entry by entry: request and response headers, cookies, URLs and query strings, post data (form, JSON, multipart), saved response bodies (base64 text included), redirects, WebSocket messages and page titles. It knows redacted values, deleted and analytics cookies, CSRF tokens and public browser keys, groups repeats per host, and reads files up to 100 MB. It never replays a request or sends the file anywhere. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, entry number, host, reason, and a safer approach. Secrets are never printed: findings name the header, cookie, parameter or field, and personal data is only counted.
What it checks
BLOCK
- H01: Authorization and Proxy-Authorization headers with a real credential, and JWTs in other headers
- H02: session cookies in Cookie and Set-Cookie headers and the HAR cookies lists
- H03: tokens, passwords, PHPSESSID and jsessionid session IDs, JWTs and signed-URL signatures (X-Amz-Signature, sig=) in URLs, redirects and Referer headers
- H04: passwords, client secrets, tokens, card numbers and JWTs in post data and sent WebSocket messages
- H05: access, refresh and ID tokens, passwords, private keys and JWTs in saved response bodies
REVIEW
- H11: API keys in URLs, fields and headers, and X-Auth-Token, CSRF and other credential headers
- H12: one-time sign-in data (OAuth codes, PKCE verifiers, SAML responses, OTP codes)
- H13: email addresses and phone numbers in URLs, bodies, WebSocket messages and page titles
- H14: requests to private IP addresses and internal host names
- H15: captures over 20 MB or with more than 1,000 requests
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example (a support capture and a test fixture), and the real report the scanner produces on the risky one
Limits It reads the HAR as written and cannot tell whether a token is still valid. Bodies stored outside the HAR (Playwright's attach mode, .zip archives), other capture formats (.chls, .saz) and personal data other than emails and phone numbers are not checked. Files over 100 MB are listed as not checked. NOT FLAGGED is not a guarantee.
Static check of HAR text. Token validity, bodies stored outside the HAR file, other capture formats and personal data other than emails and phone numbers are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example HAR files include clearly fake, inert tokens, passwords, emails and phone numbers (not-a-real-..., NOTREAL, mail.example, 555-01xx numbers) for the scanner to find. Nothing in them is replayed or sent.