Individual skill

audit-secrets

Detect env vars and secrets that reach the client through loader data, hydration state, or server-only modules imported by client code. Use for "audit secrets", "find leaked env vars", "is my API key exposed", "scan for credential leaks".

skills/audit-secrets/SKILL.md

Read pinned source

Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
106
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Pracht Audit Secrets

pracht serializes loader return values into the `pracht-state` JSON script and
hydrates the client from them. Anything a loader returns ends up readable in the
browser. The Vite plugin also strips server-only exports from route files, but
it cannot save you from a value that flows into the return.

Prerequisites: `pracht inspect` requires a vite config that registers the
pracht plugin; the env-safety report under `dist/client/_pracht/` requires a
prior `pracht build`.

MCP: if `pracht dev-mcp` is registered, prefer its `inspect_*`, `doctor`, and `verify` tools to the CLI.

## Step 0: Run the native env safety check
Back to top