T09 · Insecure Skill Coding Practices
- Location
scripts/env_doctor.py:116- Finding
Malformed Environment Lines May Disclose Secrets in Reports
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a local .env checking skill that reads files the user points it at and does not show evidence of hidden transmission, persistence, or destructive behavior.
Install only if you are comfortable with the agent reading the specific .env files you ask it to check. Treat terminal and JSON reports as sensitive, especially in CI, because malformed lines may be echoed in output.
scripts/env_doctor.py:116Malformed Environment Lines May Disclose Secrets in Reports
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
#!/usr/bin/env python3
"""Env file doctor — validate .env files, detect leaked secrets, find duplicates and issues.
Usage:
env_doctor.py <envfile> [--example EXAMPLE] [--json] [--strict]
The skill advertises file-reading behavior over potentially sensitive .env files but does not declare any explicit tool scope or permissions boundaries. That makes the capability less auditable and increases the risk that an agent may invoke the skill on secrets-bearing files without clear user-visible constraints.
The trigger phrases are broad enough to match many common requests about configuration, secrets, or validation, which can cause over-invocation of a skill that reads sensitive environment files. In a secrets-focused skill, overly broad routing increases exposure risk even if the underlying purpose is legitimate.
No suspicious patterns detected.