nodemaven-proxy
Configure NodeMaven Proxies Across Clients
Proxy integrations can fail when clients handle credentials, location parameters, or sticky sessions differently. This skill provides NodeMaven configuration guidance and exit IP checks for common HTTP clients and browser tools.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "nodemaven-proxy" from https://skillstore.io/skills/nodemaven-nodemaven-proxy.md and its manifest at https://skillstore.io/api/skills/nodemaven-nodemaven-proxy/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "nodemaven-proxy". I need a US browser session that stays consistent for ten minutes.
Expected outcome:
- Use country us, session job42, and duration 10m.
- Keep the same session parameter set throughout the flow; changing country or filter selects another exit.
- Pass Playwright proxy credentials in separate fields and keep them out of logs.
- The documented HTTP gateway does not encrypt proxy authentication; use a supported encrypted transport or trusted encrypted tunnel.
Using "nodemaven-proxy". My filter setting returns success, but the expected filter is not applied.
Expected outcome:
- Check the parameter name: filtr is ignored, while filter is the documented spelling.
- Use low, medium, or high as the filter value.
- An HTTP 200 response does not prove that every username parameter was accepted.
- Verify the exit IP separately and review the complete parameter set.
Using "nodemaven-proxy". Should each worker share the same sticky session?
Expected outcome:
- Use one distinct session identifier per worker when workers need separate exits.
- Use letters, digits, and underscores; avoid hyphens inside session values.
- Set country explicitly when location matters and choose a duration long enough for each flow.
- Omit the session identifier only when rotation between connections is acceptable.
Security Audit
SafeMost alerts are false positives from Markdown backticks, ordinary client configuration, scoped environment reads, and documented SOCKS support. Five HTTP proxy examples expose authentication credentials to network observers because the client-to-proxy connection is unencrypted, even when the destination uses HTTPS. No evidence found of prompt injection, unrelated credential collection, or covert data exfiltration.
Capability review items (5)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (50)
๐ Network access (18)
๐ Env variables (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/nodemaven-nodemaven-proxy/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/nodemaven-nodemaven-proxy?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/nodemaven-nodemaven-proxy?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nodemaven-nodemaven-proxy/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/nodemaven-nodemaven-proxy.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
nodemaven. (2026). nodemaven-proxy security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/nodemaven-nodemaven-proxy/audits/1BibTeX citation
@techreport{nodemaven-nodemaven-nodemaven-proxy-2026,
author = {nodemaven},
title = {nodemaven-proxy security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nodemaven-nodemaven-proxy/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nodemaven-proxy security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "nodemaven"
date-released: "2026-11-13"
url: "https://skillstore.io/skills/nodemaven-nodemaven-proxy/audits/1"
identifiers:
- type: other
value: "skillstore:nodemaven-nodemaven-proxy:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Connect a Python HTTP client
Configure requests with environment-based credentials, encoded proxy URLs, and an exit IP check for authorized data retrieval.
Keep browser test sessions stable
Configure Playwright proxy fields and a consistent session parameter set for multi-step regional tests.
Separate worker proxy sessions
Assign one session identifier per worker and choose explicit country and duration settings for predictable routing.
Try These Prompts
Explain which NodeMaven gateway and environment variables my Python requests project needs. Do not request or display credentials.
Prepare a Python requests configuration for Germany using environment credentials. Include URL encoding, a timeout, an exit IP check, and transport security warnings.
Configure Playwright for a US test flow with session job42 and a ten-minute duration. Keep credentials separate and explain which changes alter the session.
Review my NodeMaven worker configuration for invalid separators, unsupported parameters, session collisions, credential exposure, and rotation behavior. Propose corrections without executing network requests.
Best Practices
- Read only the required credential variables, encode credentials inside URLs, and redact proxy URLs and authentication headers from logs.
- Validate parameter names and catalogue values before connecting; keep each worker's session parameter set consistent.
- Use authorized destinations, verify the exit IP, and protect the client-to-proxy connection with a supported encrypted transport or trusted tunnel.
Avoid
- Hardcoding proxy passwords or logging credential-bearing URLs and authentication headers.
- Assuming destination HTTPS also encrypts authentication sent to an HTTP proxy.
- Guessing location values, placing hyphens inside session identifiers, or treating HTTP 200 as proof that all parameters applied.