One-click install
npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill varlock-charitablebusinessronin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: varlock
Source: https://github.com/Charitablebusinessronin/Allura_Memory/tree/main/.opencode/skills/varlock
Command: npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill varlock-charitablebusinessronin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secrets are exposed in terminals, logs, traces, or context during development and automation. Varlock enforces secure-by-default environment variable management to prevent leakage of credentials.

Core Features & Use Cases

  • Protects secrets by masking values in outputs, logs, and context.
  • Injects secrets safely at runtime for commands and scripts without leaking them.
  • Use Case: when running automation pipelines that require API keys without exposing them in history or logs.

Quick Start

Install the Varlock CLI and run your command with environment secrets injected securely.

Frequently Asked Questions about varlock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent environment variables from leaking secrets in CI/CD logs?

To prevent secret leakage in logs, you need to mask environment variables during execution. Varlock enforces secure-by-default environment variable management to mask values in outputs, logs, and context during development and automation.

What is the best way to inject API keys at runtime without exposing them in terminal history?

The best way to inject API keys safely is by using a secure runtime that validates schemas and masks secrets. Varlock injects secrets at runtime for commands and scripts without leaking them into terminal history or logs.

How does secret masking work during automated workflow execution?

Secret masking during automated workflows works by intercepting and obscuring credential values before they reach outputs. Varlock implements a secure runtime with schema validation and secret masking to prevent exposure in traces and context.

Can I use runtime secret injection across both local development and CI/CD pipelines?

Yes, runtime secret injection can be used across local development and CI/CD pipelines. Varlock works across development, CI/CD pipelines, and automated workflows where credentials are read, injected, or surfaced.

Why do my credentials show up in traces when running automation pipelines?

Credentials appear in traces because environment variables are exposed during credential handling without masking. Varlock protects secrets by preventing exposure in terminals, logs, traces, and context by enforcing secure-by-default variable management.

Do I need schema validation to safely mask secrets in command line outputs?

Schema validation is needed to accurately identify and protect sensitive values before masking them. Varlock implements a secure runtime with schema validation and secret masking to ensure secrets are not leaked in command line outputs.