authyInject secrets into subprocesses via environment variables. You never see secret values — authy run injects them directly. Use for any command that needs API...
Install via ClawdBot CLI:
clawdbot install eric8810/authyGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
$DATABASE_URLCalls external URL not in known-safe list
https://github.com/eric8810/authyAI Analysis
The skill's stated purpose is secure secret injection via a local CLI tool, and its external reference (GitHub homepage) is consistent with this purpose. However, it requires access to credential environment variables and files, which introduces a potential attack surface if the underlying `authy` binary were compromised or malicious.
Audited Apr 17, 2026 · audit v1.0
Generated Mar 22, 2026
Inject API keys and database credentials into deployment scripts without exposing secrets in CI/CD logs. Use authy run to securely pass AWS credentials, Docker registry tokens, and service connection strings to deployment tools like Ansible or Terraform.
Securely provide JWT signing keys and third-party API tokens to backend services. Each microservice runs with authy run to receive only the secrets it needs via environment variables, preventing credential sprawl across containerized applications.
Run ETL jobs and data processing scripts with database passwords and API credentials injected at runtime. Data engineers can schedule jobs that access sensitive data sources without storing credentials in script repositories or configuration files.
Provide test database credentials and mock API tokens to testing frameworks. QA teams can run integration tests against staging environments without hardcoding test credentials in test scripts or exposing them in test reports.
Securely inject payment gateway API keys and banking credentials into transaction processing scripts. Financial applications can handle sensitive payment data without storing credentials in application code or configuration files.
Sell authy as part of a comprehensive secrets management solution to large organizations. Offer enterprise features like centralized policy management, audit logging, and compliance reporting for regulated industries.
Offer authy as a SaaS product with cloud-based secret storage and team collaboration features. Target development teams with tiered pricing based on number of secrets, users, and API calls.
Provide professional services around the open source authy tool. Offer implementation consulting, custom integration development, training workshops, and premium support contracts for organizations adopting the tool.
💬 Integration Tip
Start by replacing hardcoded API keys in existing scripts with environment variables, then wrap script execution with authy run. Use --scope to limit each script to only necessary secrets.
Scored Apr 19, 2026
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope,...
Comprehensive security auditing for Clawdbot deployments. Scans for exposed credentials, open ports, weak configs, and vulnerabilities. Auto-fix mode included.
Analyze and classify agent skills for safety using local evaluation. Optionally produce a signed attestation of the vetting result.
Audit codebases and infrastructure for security issues. Use when scanning dependencies for vulnerabilities, detecting hardcoded secrets, checking OWASP top 10 issues, verifying SSL/TLS, auditing file permissions, or reviewing code for injection and auth flaws.
Security engineering workflow for OpenClaw privilege governance and hardening. Use for least-privilege execution, approval-first privileged actions, idle tim...
Git 安全扫描器 - 检查提交中的敏感信息泄露（API keys、密码、token）