Back to skill

Security audit

Generate Storybook Story

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local Storybook-writing helper with disclosed optional cloud tooling, but users should treat the optional global CLI install as a normal supply-chain decision.

You can use the standalone Storybook workflow without connecting Ritual Cloud. If you choose the optional cloud upgrade, consider installing a pinned version locally instead of globally and review what the CLI accesses before running init or status.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:80
Finding

Unpinned Global Installation of a Third-Party CLI

Content
View full analysis
Remediation
View remediation
``` 2. Prefer a project-local development dependency over a global installation, then invoke it through a package script or the local binary. 3. Commit and verify the applicable lockfile so transitive dependency versions are reproducible. 4. Document the expected npm registry and official package source to reduce dependency-confusion and registry-substitution risks. 5. Verify package provenance, signatures, or published integrity metadata before installation. 6. Review lifecycle scripts and consider installation with `--ignore-scripts` when those scripts are not required. 7. Require explicit user approval before installing the package or connecting the workspace to a cloud service. 8. Document what files, credentials, metadata, and network destinations `ritual init` and `ritual status` may access. 9. Run the CLI in a least-privilege or isolated environment when practical. ]]>
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep