embedded-payment-key
Demonstrate a credential-shaped payment key embedded in instructions
53
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./evals/skills/hardcoded-secrets/stripe-key/SKILL.mdW007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill prompt explicitly instructs the agent to use a hardcoded payment key string verbatim within instructions, which represents an insecure credential pattern.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Why it was flagged
The string `pk_test_AAAAAAAAAAAAAAAAAAAAAAAA` follows the exact format of a Stripe test API key. Although it is explicitly noted as a synthetic/inert fixture in the text and accompanying test metadata, our definition requires identifying credential-shaped strings matching known high-entropy token formats (like Stripe test keys prefixed with `pk_test_`) even if they appear to be non-functional example values. Therefore, it is flagged as a credential match.
- Repository
- cisco-ai-defense/skill-scanner
- Commit
c3d7fd9
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.