SKILLEMALL.ai
GitHub ↗ RU Sign in

BB aws-secrets-scanner

Detect hardcoded secrets, exposed API keys, and credential misconfigurations in IaC and config files

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 838 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Detect hardcoded secrets, exposed API keys, and credential misconfigurations in IaC and config files

As a process B 68/100 · Nearly there — weak spots: when it triggers, consistency, running it twice

IntegrationAWSInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
95
Quality 40%
69
Run on models
none yet
Process rating
B
68/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Secrets in code medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Secrets in code secret-private-key SKILL.md:62
    Private key material (key header without key body; quoted — discussed, not commanded)
    - Private SSH keys (`-----BEGIN PRIVATE KEY----- …
    header onlyquoted

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "pack"
  • note frontmatter-key unknown frontmatter key "tier"
  • note frontmatter-key unknown frontmatter key "price"
  • note frontmatter-key unknown frontmatter key "permissions"
  • note frontmatter-key unknown frontmatter key "credentials"

Process rating: all ten parameters 68/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (aws-secrets-scanner) differs from the folder (secrets-scanner)
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 26 steps
  • 100Execution cost. Instruction body is 838 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 100: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 26 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.