secret

Store, retrieve, rotate, and scan for leaked secrets across providers.

39|6|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/the-agency-ai/the-agency --skill secret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret
Source: https://github.com/the-agency-ai/the-agency/tree/main/src/claude/skills/secret
Command: npx skills add https://github.com/the-agency-ai/the-agency --skill secret

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of sensitive secrets, enabling secure storage, retrieval, and rotation to protect critical information.

Core Features & Use Cases

  • Secret Storage and Retrieval: Set, get, delete, and list secrets using various providers like Vault or AWS.
  • Secret Rotation: Automate secret rotation workflows to enhance security.
  • Codebase Scanning: Detect leaked secrets in code repositories, preventing accidental exposure.
    Use Case: Developers can securely update API keys or database credentials across services without manually handling the secrets or risking leaks by storing secrets in code.

Quick Start

To store a new secret using the configured provider, specify the secret name and value in your command to securely update your credentials.

Frequently Asked Questions about secret

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

FAQPage Schema
How do I automate secret rotation across AWS and Vault?

Automating secret rotation across AWS and Vault requires configuring provider-compatible workflows that securely update credentials without manual handling. This enforces strict security best practices and safe credential lifecycle management.

What is the best way to scan a codebase for leaked secrets?

Scanning a codebase for leaked secrets involves analyzing repositories to detect exposed credentials and prevent accidental exposure. This identifies hardcoded secrets to protect critical information within integrated workflows.

Can I use this to manage secrets across multiple cloud providers?

Managing secrets across multiple cloud providers is supported by setting, getting, and deleting credentials across compatible platforms. This simplifies secure storage and retrieval for developers and administrators.

How do I store and retrieve secrets securely in my codebase?

Storing and retrieving secrets securely requires using configured vault providers to update API keys or database credentials. This prevents risking leaks by avoiding hardcoded secrets directly in code repositories.

Does secret management work without manually handling credentials?

Secret management works without manually handling credentials by automating routine lifecycle tasks within integrated workflows. This allows developers to securely update credentials across services while maintaining strict provider compatibility.