keychain-manager

Name: keychain-manager
Availability: InStock
Author: jitsu

Store, retrieve, rotate, and delete macOS Keychain secrets via the security CLI.

1|Updated Apr 13, 2026

Search Tags:#macos #secrets #keychain #token-management #credential-storage #security-cli

Ready to run

npx skills add https://github.com/0xjitsu/jitsu-skills --skill keychain-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keychain-manager
Source: https://github.com/0xjitsu/jitsu-skills/tree/main/skills/keychain-manager
Command: npx skills add https://github.com/0xjitsu/jitsu-skills --skill keychain-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages secrets and API keys in the macOS Keychain using the security CLI. Triggered when a user asks to store, retrieve, list, rotate, or delete tokens and credentials. Uses a consistent naming convention with the bbmisa account and uppercase service names. Never exposes secrets in plaintext output or commits them to git.

Core Features & Use Cases

Store, retrieve, rotate, and delete secrets in the macOS Keychain via the security CLI.
Enforces a consistent naming convention with account "bbmisa" and uppercase service identifiers to prevent leaks.
Use Case: Automate secure credential management for developers, CI/CD pipelines, and local workflows without exposing secrets.

Quick Start

Store, retrieve, or rotate a secret in the macOS Keychain using the security CLI with the bbmisa account.

Frequently Asked Questions about keychain-manager

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

FAQPage Schema

How do I securely store and retrieve API tokens in the macOS Keychain via the security CLI?▼

To securely store and retrieve API tokens in the macOS Keychain, use the security CLI with a consistent naming convention. This approach enforces the bbmisa account and uppercase service identifiers to prevent plaintext exposure and credential leaks.

What is the best way to manage GitHub and DevOps service credentials locally on macOS without exposing secrets?▼

The best way to manage service credentials locally is by storing them in the macOS Keychain. This ensures secure credential storage and access for DevOps pipelines without exposing secrets in plaintext output or committing them to git.

How do I rotate and delete secrets in the macOS Keychain using command line tools?▼

You can rotate and delete secrets in the macOS Keychain by executing specific commands via the security CLI. This workflow maintains secure token management by replacing outdated credentials and removing unused ones safely.

Does macOS Keychain token management prevent committing secrets to git repositories?▼

Yes, macOS Keychain token management prevents committing secrets to git by avoiding plaintext exposure entirely. Credentials are stored securely via the security CLI, ensuring sensitive data remains outside your local working directory and version control.

Can I use the macOS security CLI to enforce a consistent naming convention for credential storage?▼

Yes, using the macOS security CLI for credential storage enforces a consistent naming convention. It applies the bbmisa account name and uppercase service identifiers, which organizes tokens systematically and helps prevent accidental leaks.