Forge-Secrets-Management

Manages secrets inventory, injection policy, rotation, and leakage verification across the software lifecycle.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-secrets-management-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Secrets-Management
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/05-Security/Forge-Secrets-Management
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-secrets-management-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Credentials, keys, and tokens often end up hardcoded in source control, build artifacts, or logs, creating serious security exposure. This Skill defines a policy-driven discipline for managing every secret's lifecycle — storage, injection, rotation, and retirement — so no secret material leaks into repositories, pipelines, or logs. ## Core Features & Use Cases - Secrets Inventory & Policy: Maintains a complete inventory of every secret with owner, scope, storage location, and rotation schedule, plus injection policy favoring identity-based mechanisms. - Leakage Verification: Sweeps repositories (including history), build artifacts, images, configuration, and logs for secret material, routing confirmed exposures to defect management. - Rotation & Incident Response: Executes scheduled and emergency rotation, verifies consumer transition, and coordinates with incident management on confirmed exposure. - Use Case: When a code review flags a hardcoded API key, use this Skill to classify the finding, trigger immediate rotation, assess the impact window, and update the secrets inventory and policy. ## Quick Start Apply the Forge-Secrets-Management skill to build a secrets inventory and define storage, injection, and rotation policy for my new service and its CI/CD pipeline.

Frequently Asked Questions about Forge-Secrets-Management

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

FAQPage Schema
How do I manage secrets across the software development lifecycle?▼

Maintain a secrets inventory listing every secret with its owner, scope, storage location, and rotation schedule, then define injection and rotation policy per secret. Verify regularly that no secret material appears in repositories, artifacts, or logs, and rotate immediately on confirmed exposure.

How to detect hardcoded secrets in source code and git history?▼

Perform leakage verification sweeps across repositories including full history, build artifacts, container images, configuration files, and logs. Classify any findings by severity and route confirmed exposures to defect management while triggering immediate rotation.

What is the best way to inject secrets into applications at runtime?▼

Prefer identity-based injection mechanisms over distributing secret material, and never place secrets in source control, build artifacts, or logs. The specific vault or platform tooling is a project-level decision governed by the injection policy.

When should secrets rotation be performed?▼

Rotate secrets on a defined schedule recorded in the inventory, and immediately upon any suspected or confirmed exposure. After rotation, verify that all consumers have transitioned before retiring the superseded secret.

Does this skill replace secrets management tools like vaults?▼

No, it defines the policy and verification discipline rather than operating specific vault tooling. Concrete secret stores and platform mechanisms remain project-level implementation choices that must conform to the defined policy.