Back to skill

Security audit

API credentials hygiene

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation-focused helper for safer API credential handling and does not include hidden execution, exfiltration, or persistence behavior.

Install only if you want help documenting and hardening credential handling. Provide redacted snippets or variable names rather than real API keys, tokens, or private keys, and review any generated template before using it in a project.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Instruction Override

High
Category
Prompt Injection
Confidence
90% confidence
Finding

This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 19)May include surrounding context.

md
- Create an environment variable map and a secure .env template for this project.
  - Set up credential separation for dev versus prod with clear audit trails.
- DO NOT USE WHEN…
  - You want to obtain keys without authorization or bypass security controls.
  - You need legal/compliance sign-off (this outputs technical documentation, not legal advice).

## INPUTS

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 16)May include surrounding context.

md
# assets/dotenv-template.example
# Copy to .env (do not commit). Replace values via secret manager or deploy-time injection.

ENVIRONMENT=dev
APP_NAME=

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · assets/dotenv-template.example.md (reported line 2)May include surrounding context.

md
# assets/dotenv-template.example
# Copy to .env (do not commit). Replace values via secret manager or deploy-time injection.

ENVIRONMENT=dev
APP_NAME=

Static analysis

No suspicious patterns detected.