Bastion Protocol v3.5

Derive service-specific credentials from a root secret and context metadata.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/imkevinchasse/Bastion-Enclave-repo-V2 --skill bastion-protocol-v3-5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bastion Protocol v3.5
Source: https://github.com/imkevinchasse/Bastion-Enclave-repo-V2/tree/main/public
Command: npx skills add https://github.com/imkevinchasse/Bastion-Enclave-repo-V2 --skill bastion-protocol-v3-5

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill acts as an autonomous steward for your digital identity, providing secure and deterministic credential derivation without relying on external servers or persistent storage.

Core Features & Use Cases

  • Deterministic Credential Derivation: Generates service-specific credentials from a root secret and context metadata.
  • Stateless Operation: All outputs are computed locally, ensuring no data is stored or synced externally.
  • Secure Vault Management: Provides methods to securely unlock, access, and save encrypted vault data via both browser and CLI interfaces.
  • Use Case: Securely generate unique, strong passwords for every online service without a traditional password manager, ensuring your root secret is the only thing you need to protect.

Quick Start

Use the Bastion Protocol skill to unlock the vault using the provided master password.

Frequently Asked Questions about Bastion Protocol v3.5

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

FAQPage Schema
How do I generate service-specific passwords without a traditional password manager?

You can generate service-specific passwords by deriving them deterministically from a root secret and context metadata. This stateless approach computes credentials locally, eliminating the need for external servers or persistent storage.

How does stateless credential derivation protect against offline brute-force attacks?

Stateless credential derivation protects against brute-force attacks by computing outputs locally without syncing data externally. It uses a root secret to generate unique credentials, ensuring exfiltrated vault data remains useless to attackers.

Can I manage my secure vault using a headless Java CLI environment?

Yes, you can manage your secure vault using a headless Java CLI. The protocol supports both visual browser-based interactions and CLI commands to unlock, access, and save encrypted vault data.

What is the best way to securely manage digital identity without external servers?

The best way to manage digital identity statelessly is by deriving credentials from a root secret and context metadata. This ensures all outputs are computed locally without relying on external servers or persistent storage.

Do I need persistent storage to compute deterministic credentials?

No, you do not need persistent storage to compute deterministic credentials. The protocol operates statelessly, generating all service-specific outputs locally from your root secret and context metadata.

Why should I use deterministic password generation over traditional password managers?

Deterministic password generation computes credentials locally from a root secret, preventing credential exfiltration risks associated with traditional password managers. This stateless operation ensures your root secret is the only component requiring protection.