memory-first-secret-search

What problem does it solve?

It prevents unsafe, scattered attempts to locate credentials by enforcing a strict first step: consult the canonical secrets index before any token, API key, password, SSH key, or secret hunting.

Core Features & Use Cases

• Canonical-first enforcement: Blocks searching across random filesystem paths (e.g., .env files, containers, home directories) prior to reading memory/_INDEX-SECRETS.md.
• Pointer-driven access: Resolves each secret by following the index’s prescribed location and exact access method for known environments (e.g., Hostinger hPanel references, CT 100 paths, Vault items, DB table routes).
• Rotation-aware handling: Detects missing or expired secrets and converts the situation into an explicit rotation/updates workflow (update index status, propose the correct provision steps, and avoid treating it as a false Tier 0 gap).

Quick Start

Ask your agent to retrieve a specific credential (for example, “I need the Hostinger token for API access”), and instruct it to read memory/_INDEX-SECRETS.md first, then follow the indexed pointer for that exact secret.