creds

Manage bug bounty credentials across targets with token-based authentication flows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AshtonVaughan/bountyhound --skill creds-ashtonvaughan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creds
Source: https://github.com/AshtonVaughan/bountyhound/tree/main/bountyhound/skills/creds
Command: npx skills add https://github.com/AshtonVaughan/bountyhound --skill creds-ashtonvaughan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security teams manage credentials for bug bounty targets, enabling loading, storing, refreshing, and creating test accounts to support authenticated testing.

Core Features & Use Cases

  • Credential lifecycle management: load, store, refresh, and create test accounts for authorized testing workflows.
  • Environment-driven workflows: standardizes .env credential formats and memory identity references to streamline re-authentication.
  • Use Case: When starting a new target, quickly bootstrap accounts and inject credentials to accelerate authorized testing.

Quick Start

Register accounts, store credentials in the designated .env file, and load them to initiate authenticated testing.

Frequently Asked Questions about creds

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

FAQPage Schema
How do I manage bug bounty credentials for authenticated testing across multiple targets?

Manage bug bounty credentials by loading, storing, refreshing, and creating test accounts within a standardized .env format to support authorized testing workflows across targets. This approach streamlines re-authentication and securely handles token-based authentication flows.

What is the best way to automate token refresh cycles during security testing?

Automate token refresh cycles by applying credential workflows that handle token-based authentication flows automatically. This ensures your authenticated testing sessions remain active without manual re-authentication interruptions during long testing periods.

Can I use .env files to handle multi-user IDOR scenarios?

Yes, you can use .env files to handle multi-user IDOR scenarios by storing multiple test account credentials and applying memory identity references. This allows you to quickly switch between authenticated user contexts during authorization testing.

How do I bootstrap test accounts when starting a new bug bounty target?

Bootstrap test accounts by registering new users and storing their credentials in the designated .env file. You can then load these credentials to immediately initiate authenticated testing and accelerate your authorized workflow on the target.

Do I need a specific environment format for storing bug bounty credentials?

You need to use a defined .env format for storing bug bounty credentials. This enforces a standardized structure for environment-driven workflows, ensuring secure and consistent credential loading across your testing setup.