doppler

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The skill instructs embedding and printing secrets verbatim (e.g., inline API keys, tokens passed via --token, and using --plain to output secret values), which requires the agent to handle or output secret values directly and thus poses an exfiltration risk.

HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

• Secret detected (high risk: 1.00). I inspected the skill files for literal credential values. I flagged the API key-like literal at SKILL.md:99 because it appears as a concrete API key value (API_KEY="sk-live-abc123def456") rather than a clearly marked placeholder or truncated/redacted string — it follows a real API-key pattern and is presented as a literal in the docs.

I ignored the following obvious non-secrets or placeholders:

• STRIPE_KEY="sk_live_..." (SKILL.md:103) and STRIPE_KEY="sk_live_51HG4..." (SKILL.md:229) — truncated with ellipses, treated as redacted/truncated examples.
• STRIPE_KEY="sk_test_your_stripe_test_key_here" (SKILL.md:221) — explicitly a test/example placeholder.
• export DOPPLER_TOKEN="dp.st.prd.xxxx" and inline --token="dp.st.prd.xxxx" (SKILL.md:174-176) — contain "xxxx" placeholder fragments, not a real token.
• Other values (database URLs, hostnames, ports, simple strings like "debug", "warn") are configuration examples or low-entropy setup values and not secrets per the rules.