langsmith-fetch

Warn

Audited by Gen Agent Trust Hub on Jun 30, 2026

Risk Level: MEDIUMCREDENTIALS_UNSAFEEXTERNAL_DOWNLOADSCOMMAND_EXECUTIONPROMPT_INJECTION
Full Analysis
  • [EXTERNAL_DOWNLOADS]: The skill requires the installation of the langsmith-fetch package via pip. This is not a standard or official package from the LangChain organization (which typically uses langsmith), and its source is unverifiable within the skill's instructions.
  • [CREDENTIALS_UNSAFE]: The instructions direct the agent to verify the LANGSMITH_API_KEY by printing it to the terminal using echo $LANGSMITH_API_KEY. This can lead to sensitive credentials being captured in logs or command history. Furthermore, the skill suggests persisting these credentials by appending them to ~/.bashrc or ~/.zshrc, which is an insecure practice for secret management and a form of persistence.
  • [COMMAND_EXECUTION]: The skill relies heavily on shell command execution for setting up environment variables, creating directories with timestamps, and performing file operations like grep on JSON data. While these are common for developer tools, they provide a broad surface for command injection if user inputs are improperly handled.
  • [PROMPT_INJECTION]: The skill is susceptible to indirect prompt injection (Category 8). It fetches trace data from an external API (LangSmith) and processes it to identify execution patterns and errors.
  • Ingestion points: External traces are fetched into recent-traces.json (SKILL.md, Workflow 4) and then analyzed by the agent.
  • Boundary markers: None. There are no instructions or delimiters to help the agent distinguish between its own logic and malicious instructions that might be embedded in the fetched trace data (e.g., in error messages or tool outputs).
  • Capability inventory: The skill has capabilities for file system writes (mkdir, >> ~/.bashrc), network access (via langsmith-fetch), and shell execution.
  • Sanitization: No evidence of sanitization or validation of the fetched trace content is present.
Audit Metadata
Risk Level
MEDIUM
Analyzed
Jun 30, 2026, 04:03 PM