caddy-security secrets manager Caddyfile configuration. Use when creating, reviewing, or modifying security secrets blocks, external security.secrets modules, static secrets manager examples, AWS secrets manager examples, secret IDs, secret-backed user data, authdbctl-generated password or API key hashes, secret-backed crypto keys, and integration with runtime replacement.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
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.
I flagged multiple high-entropy literal values that appear to be real secrets rather than placeholders. Rationale: - Bcrypt payloads (lines 57, 58, 142, 167) are high-entropy strings and the doc explicitly treats bcrypt password/api_key payloads as the final secret values expected by the system, so they qualify as secrets under the policy. - The 24-character-looking API key/plaintext prefix (lines 106 and 172: "XnxJ5W0AAcDb2FO1nefd35fT") is a non-trivial, high-entropy token-like string that could represent an API client secret/prefix and is not a simple placeholder. I did not ignore these as examples because they are neither trivial placeholders (e.g., YOUR_API_KEY) nor simple setup passwords; they are complex, high-entropy literals that meet the definition of secrets.
b96087f
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.