keychain-hermes

Name: keychain-hermes
Availability: InStock
Author: prince3626ezechiel-lang

Inspect Hermes OS keychain stores for plaintext credentials and Git history secrets.

Updated Jul 5, 2026

Search Tags:#GPG #credential security #keychain audit #secret store #plaintext detection

Ready to run

npx skills add https://github.com/prince3626ezechiel-lang/ivoire-monade-palantir --skill keychain-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keychain-hermes
Source: https://github.com/prince3626ezechiel-lang/ivoire-monade-palantir/tree/main/keychain-hermes
Command: npx skills add https://github.com/prince3626ezechiel-lang/ivoire-monade-palantir --skill keychain-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keychain and secret store vulnerabilities expose sensitive information. This Skill identifies and rectifies such vulnerabilities in Hermes OS.

Core Features & Use Cases

Secret Store Audit: Inspects local keychain directories for plaintext exposure.
GPG Vault Verification: Checks the status of GPG-protected secrets.
Git History Analysis: Ensures no secrets are committed to Git history.
Recommendations: Advises on vaulting and rotation for exposed secrets.

Quick Start

Run 'keychain-hermes' to initiate the audit of your Hermes OS keychain and secrets.

Frequently Asked Questions about keychain-hermes

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

FAQPage Schema

How do I check if my API credentials and wallet seeds are exposed in plaintext?▼

To check for plaintext exposure of API credentials and wallet seeds, you need to scan local keychain directories. This process inspects secret stores to verify sensitive tokens and keys are securely vaulted rather than left readable.

How do I scan Git history for committed secrets and sensitive data?▼

Scanning Git history for committed secrets involves analyzing past commits for exposed tokens or keys. This audit checks repository history to ensure sensitive data was never accidentally committed and recommends remediation if found.

What is the best way to verify GPG vault status for local secret stores?▼

Verifying GPG vault status involves checking the protection state of GPG-encrypted secrets within your local environment. This audit inspects the keychain to confirm that GPG-protected credentials are properly configured and actively secured.

How do I audit keychain secrets on Hermes OS for security vulnerabilities?▼

Auditing keychain secrets on Hermes OS requires inspecting local keychain directories for plaintext exposure and GPG vault status. The scan identifies vulnerable tokens, seeds, and keys, then recommends vaulting or rotation actions.

What actions should I take after finding plaintext tokens in my secret store?▼

After finding plaintext tokens in your secret store, you should immediately vault the exposed credentials and rotate the compromised keys. The audit provides specific recommendations for securing or replacing any sensitive data identified.

Does the secret store audit work without external dependencies?▼

Yes, the secret store audit works without external dependencies, relying solely on internal scripts. It independently inspects local directories, verifies GPG status, and scans Git history to detect exposed credentials.